Repo-local knowledge-base workflow for querying and maintaining the Turso-backed markdown index. Use when you need prior plans, reports, specs, or other tracked KB content before broader manual repo scans.
Use this skill whenever the task depends on repository memory: prior plans, reports, specs, or other KB-tracked markdown. This skill makes the local KB the first retrieval step before broader document scans or code search.
The local KB is built from tracked markdown, currently centered on paths such as:
docs/plan/**/*.mddocs/report/*.mddocs/specs/*.mdIf a paper, note, or extracted result should become searchable, convert or summarize it into tracked markdown first, then sync that markdown into the KB. Do not claim that tursodb ingests PDFs directly.
Choose the narrowest command that matches the retrieval need.
| Need | Command | Why |
|---|---|---|
| General repo-memory lookup with both wording and concept recall | devenv shell -- search-kb "query text" | Hybrid retrieval combines lexical and vector signals. |
| Exact terms, known phrases, spec wording, file titles | devenv shell -- search-kb-fts "query text" | Best when the wording itself matters. |
| Approximate semantic recall, paraphrases, concept lookup | devenv shell -- search-kb-vector "query text" | Best when the right wording is unclear. |
Use maintenance commands only when the indexed markdown set has changed or when the KB is missing.
devenv shell -- rebuild-kb
.turso/knowledge.db from the tracked markdown sources.devenv shell -- sync-kb [path ...]
docs/.sync-kb for the touched file or rebuild-kb when a full refresh is needed.When using this skill, return structured retrieval notes with:
Stop and report instead of guessing when:
The correct fallback is to read the relevant tracked markdown directly and, if needed, refresh the KB.