Codex Scribe doc-maintainer for a Source-Backed DOCS.MD
Map Scribe subsystems and user-facing flows to real source paths. This workflow keeps DOCS.MD and its table of contents in sync after a module or behavior change.
中文Install in Codex
Codex with a Scribe checkout and access to DOCS.MD and the affected code.
- Copy the entire pinned `.codex/skills/doc-maintainer/` directory to `.agents/skills/doc-maintainer/` in the target checkout.
- Open Codex in that checkout and invoke `$doc-maintainer` with the example task and desired output.
Example task
After adding an example export module in a scratch checkout, invoke `$doc-maintainer`. Ask it to document the module's entry files and verify the table-of-contents target.What to check
DOCS.MD names the module's responsibility and entry files. Its table of contents links to the corresponding section.
Original SKILL.md on GitHub · Updated
Frequently asked question
When is a separate section appropriate?
Give complex features focused coverage and update the table of contents. Ordinary module coverage can go in the codebase map.