← ClaudeAtlas

lookuplisted

Search the repo's .knowledgebase/ of findings, learnings, and decisions. Use before starting an investigation, debugging session, or design work in a repo that has .knowledgebase/, or when asked what is already known about a topic.
simonpokorny/knowledgebase · ★ 0 · AI & Automation · score 58
Install: claude install-skill simonpokorny/knowledgebase
Check what the repo already knows before rediscovering it. Entries are 700 bytes max by contract, so this costs two greps and a few file reads. 1. Skim every title first. A title IS a complete claim; this alone often answers the question: ```bash grep -rh '^# ' .knowledgebase/entries 2>/dev/null ``` 2. Narrow by keyword, scope, or type (the type is the filename prefix): ```bash grep -ril '<keyword>' .knowledgebase/entries grep -rl 'scope: <scope>' .knowledgebase/entries ls .knowledgebase/entries/decision-*.md ``` 3. Read the matching files in full. Reading what you found: - Trust `verified` over `unverified`. Treat `stale` as a hypothesis; if you re-verify it, bump its `status` and `date`. - A `superseded` decision explains history, not current truth. The superseding entry names what it replaces. - A learning with a `guard:` is an enforced rule. Do not plan work that fights it. Tell the user which entries you used, so the base visibly pays rent. If lookup finds nothing and your own investigation then establishes the answer, that is exactly the entry the base was missing: record it with the `/note` skill before finishing.