Menu
{{ ƔƔƔ }} Update an existing documentation file to reflect recent code changes
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
{{ 𝚫𝚫𝚫 }} Rebuild roadmap-system.zip, the distributable snapshot of the roadmap tooling (scripts, HTML template, conventions reference, and every roadmap-touching skill, including this one).
{{ 𝛀𝛀𝛀 }} Create a project roadmap in the rich phase-array format — roadmaps.json as source of truth plus a PHASE task list and prose overview
{{ 𝛀𝛀𝛀 }} Recompute and synchronise roadmap task statuses across roadmaps.json and its projections, with optional codebase reconciliation
{{ 𝛀𝛀𝛀 }} Add a task to a rich-format project roadmap with correct ID, dependency wiring, and graph integrity — ID assignment, status computation, dependency edges in both directions, and no unconnected islands.
Git workflow: branch management, commit conventions, PR patterns, conflict resolution.
{{ 𝛀𝛀𝛀 }} Review a pull request and post it as a GitHub review
| name | Docs: Update Target |
| description | {{ ƔƔƔ }} Update an existing documentation file to reflect recent code changes |
| when_to_use | When a doc (other than README or an ADR) has drifted from the code and needs its content reconciled with what actually shipped since it was last touched. |
| model | sonnet |
| disable-model-invocation | true |
| allowed-tools | ["Read","Glob","Grep","Edit","Bash(git:*)","Bash(~/.claude/library/scripts/git-doc-history.sh:*)"] |
| argument-hint | ["doc path or name","e.g. Technical-Overview"] |
Analyse recent code changes and update the specified documentation file. (For READMEs specifically, use doc-readme — this skill covers everything else: technical overviews, ADRs, guides.)
Resolve the doc from $ARGUMENTS (a path, or a name to Glob for under docs/). If nothing was given or nothing matches, ask — do not guess which doc was meant.
Read the doc to understand its structure and style, then gather what changed in one command:
"$HOME"/.claude/library/scripts/git-doc-history.sh {doc-path} {scope-dir}
Pass the code directory the doc describes as the scope (default: the doc's own directory, which is rarely right for docs living under docs/ — pick the source dir it documents).
Identify specific updates needed: outdated sections, missing coverage of new behaviour, stale examples.
Generate updates preserving the existing structure; show a diff; apply on approval.
Update any timestamp in the doc's frontmatter.