use-code-wiki
Skill1 starsChanged 5 months agoMITView on GitHub
Navigate a documented Git repository through .code-wiki/wiki.json to locate implementation files, plan changes, and answer codebase-structure questions. Use when a Code Wiki index exists and repository exploration should proceed from summaries to headers to full source.
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 6 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use the Code Wiki as a progressive navigation cache.
- Very specific: line 14
Run python3 scripts/query_index.py --root <absolute-root> --json status from this skill directory.
- Very specific: line 15
If the index is absent, invalid, or unsupported, stop using it and recommend build-code-wiki.
- Very specific: line 16
Run python3 scripts/query_index.py --root <absolute-root> --json show .
- Distinctive: line 19
Read the managed headers of shortlisted files.
- Distinctive: line 20
Read complete files only when implementation detail is required or an entry is stale.
- Distinctive: line 21
Read adjacent tests and configuration before editing.
- Distinctive: line 22
Verify claims against current source before answering or modifying code.
- Very specific: line 27
Use show <relative-path> for one repository, directory, or file node.
- Very specific: line 28
Use stale only when freshness affects the task.
- Very specific: line 29
Never pass absolute paths or paths containing ...
- Distinctive: line 30
Do not load the complete index when targeted subtree queries are sufficient.
- Very specific: line 32
Read wiki.schema.json only when schema interpretation or validation detail is required.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Use Code Wiki
Use the Code Wiki as a progressive navigation cache. Treat current source code as authoritative.
Workflow
- Resolve the target Git root.
- Run
python3 scripts/query_index.py --root <absolute-root> --json statusfrom this skill directory. - If the index is absent, invalid, or unsupported, stop using it and recommend
build-code-wiki. - Run
python3 scripts/query_index.py --root <absolute-root> --json show .for repository orientation. - Query only directory nodes relevant to the request.
- Shortlist files from their summaries.
- Read the managed headers of shortlisted files.
- Read complete files only when implementation detail is required or an entry is stale.
- Read adjacent tests and configuration before editing.
- Verify claims against current source before answering or modifying code.
- Recommend
build-code-wikiafter source changes.
Query operations
- Use
show <relative-path>for one repository, directory, or file node. - Use
staleonly when freshness affects the task. - Never pass absolute paths or paths containing
... - Do not load the complete index when targeted subtree queries are sufficient.
Read wiki.schema.json only when schema interpretation or validation detail is required.
In this repository31 other files it gives its agents.
- skills/book-to-skill/AGENTS.mdAGENTS.md
- skills/book-to-skill/CLAUDE.mdCLAUDE.md
- ai-paper-digestSkill
- battery-statusSkill
- book-to-skillSkill
- codebase-mapSkill
- codebase-overviewSkill
- codebase-summarySkill
- concept-wiki-htmlSkill
- frontend-designSkill
- gh-address-commentsSkill
- gh-fix-ciSkill
- githubSkill
- grounded-file-qaSkill
- imagegenSkill
- learn-codebaseSkill
- lecture-note-writerSkill
- ning-python-scientific-plottingSkill
- openai-docsSkill
- plugin-creatorSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
- repo-quick-scanSkill
- review-agentSkill
- skill-creatorSkill
- skill-installerSkill
- yeetSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.