Docs
Agent skills for taking work from idea to merged PR
npx -y skills add magarcia/skills --skill docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Find and fix repository documentation that a code change made false, including AGENTS.md, README files, docs, ADR references, command examples, APIs, configuration, and environment variables. Use after architectural or interface changes, renames, workflow changes, behavior-preserving refactors, or as the documentation stage between $implement and $ship in $build.
SKILL.md
2.0 KB, as published. Nobody here has run it
Docs
Gate on the diff: did it change architecture, an API, CLI, configuration, environment variable, build/test/deploy workflow, or the approach the project uses? If not, give one line of reasoning and stop.
- Inventory — Read every applicable
AGENTS.mdand the documentation it references. Inventory root and module READMEs,docs/, ADR directories, API specifications,.env.exampleand sample configuration, and in-repo diagrams. If the repository containsCLAUDE.md, inspect it as documentation that may also have become stale, not as Codex instruction authority. - Cross-reference — Use
rgto search documentation for identifiers, paths, commands, and concepts removed or changed by the diff. Old identifiers are often the best signal because stale documentation still uses them. Give applicableAGENTS.mdfiles priority: false commands, structure, or conventions there misdirect future work. - Fix — Update factual rot in place: commands, paths, names, snippets, configuration examples, and diagram sources. Run examples where feasible. Limit changes to documentation invalidated by the diff; do not rewrite unrelated prose.
- Flag — List decisions that need human authorship and external documentation pages that remain stale. Do not mutate an external documentation system unless the user explicitly placed it in scope.
Report what was updated, confirmed accurate, or flagged.
- Write documentation as current state, without migration-history narration.
- Update the source of generated documentation, never generated output.
- Treat plausible, almost-correct documentation as higher risk than obviously obsolete material.