code-wiki

Run the code-wiki skill against a local path or GitHub URL. It scans the repository structure, selects 8-10 core modules, and writes a README, architecture doc, per-module deep-dives, and Mermaid diagrams to ~/.robo/wikis/<repo-name>/.

The skill reads entry points and key files, then writes flowchart, classDiagram, and sequenceDiagram blocks into markdown files. Every diagram node is verified against real components in the source to avoid fabricated architecture.

Yes, it works on local directories, the current working directory, or any git-cloneable URL including private repos. Cloned repos go to a temp directory and output defaults to ~/.robo/wikis/, never into the repo unless explicitly requested.

It is language-agnostic with heuristics for Python, JavaScript/TypeScript, Rust, and Go module layouts. For languages without classes like Go or C, class diagrams are replaced with struct relationships or prose explanations.

Skip it for single-file or single-function questions, one-off API endpoint lookups, and codebases you are actively editing in the session. It produces reference documentation, not strategic narrative about why a project exists.

The skill writes a .codewiki-state.json with the source SHA. On re-run it compares SHAs and offers to regenerate only modules whose files changed, using git diff between the old and current commits.