Audit project documentation for staleness against current branch code changes.
npx skills add https://github.com/vr000m/skills.md --skill update-docs-vr000m
Please help me install this Agent Skill. Skill: update-docs Source: https://github.com/vr000m/skills.md/tree/main/.claude/skills/update-docs Command: npx skills add https://github.com/vr000m/skills.md --skill update-docs-vr000m
Syncs project documentation with code changes on the current branch by scanning dev plans, changelogs, READMEs, AGENTS.md, and PR descriptions for staleness against the actual diff, then offering targeted updates. Use after finishing implementation work, before creating or merging a PR, or when the user says "update docs" or "/update-docs".
Run the update-docs command after finishing implementation work to synchronize documentation with the latest code changes.
High-intent search queries and answers about installing and using this skill.
To keep your README and changelog updated after code changes, audit your documentation against the current branch's diff. This identifies staleness like outdated command references or missing checkboxes, allowing you to apply targeted edits that synchronize project docs with the latest codebase modifications.
Syncing dev plans with your current branch diff involves comparing the plans against actual code changes. This process scans for staleness, proposes targeted updates to reflect the new state of the codebase, and ensures your development plans accurately match the implemented features.
You can update PR descriptions before merging by auditing them for staleness against the codebase diff. This supports a PR workflow by identifying outdated architecture notes or missing details, then optionally applying the documentation updates automatically to align with the latest changes.
Auditing AGENTS.md files for staleness against codebase modifications requires scanning the file alongside the current branch's diff. It detects outdated architecture notes or command references, then offers targeted edits to adjust the documentation and accurately reflect the latest code changes.
You need to refresh project documentation to match code after finishing implementation work and before creating or merging a pull request. This ensures your dev plans, changelogs, and READMEs are audited for staleness against the actual diff and updated to reflect the latest state.
Hameem1Completes project wrap-up including linting, validation and commit for a session.
shellicarGenerate effect-focused commit messages, PR titles, and work item descriptions.
coroborosCorrect grammar and spelling in Markdown and documentation files.
fycd2006Generate user-facing changelog entries from Git commit history.
