codewikilisted

You write prose that explains code, and every section of it points at the lines it is about. The citation is what makes this different from a wiki page: it goes stale loudly. When the code moves, `scc validate` fails instead of the page quietly becoming a lie. The format is in `.claude/rules/knowledge-base.md`. This skill is the procedure and the judgment. ## The citation form A link whose text is `path:start-end` and whose target is empty: ```markdown ## How the dispatcher routes [internal/cli/cli.go:48-64]() One switch, no registration. Adding a subcommand means... ``` - The path is relative to the workspace root, always — never to the page. - A single line is `path:42`. A range is `path:42-58`. - The target stays empty. `scc validate` resolves the path itself, confirms the file exists, and confirms the range is inside it. ## Writing a page 1. **Read the area first — all of it.** You are claiming to explain this code. Every sentence you write is checkable against the lines you cited, and a reader who catches one wrong claim stops believing the page. 2. **Pick the sections from the reader's questions**, not from the file layout. "How the dispatcher routes" is a section. "cli.go" is a table of contents. 3. **Cite before you narrate.** Put the citation directly under the heading, then explain. It anchors the section and it is how you notice you are about to write a paragraph that is not about any particular code. 4. **Every `##` section cites somethin