Reconcile repository documentation with actual code and configuration.
npx skills add https://github.com/ChazzCoin/claude-kit --skill update-docs-chazzcoin
Please help me install this Agent Skill. Skill: update-docs Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/update-docs Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill update-docs-chazzcoin
Pause and reconcile documentation against reality. Walks every core doc — README, CLAUDE.md, DEPLOY.md, task-rules, PHASES, ROADMAP, AUDIT, .env.example, skill files — and flags what's drifted from the actual state of the code, then proposes targeted edits. Triggered when the user wants a doc-sync pass — e.g. "/update-docs", "let's check our docs", "are our docs still accurate", "make sure everything is documented properly".
Activate a doc-sync pass by issuing /update-docs and reviewing the proposed changes.
High-intent search queries and answers about installing and using this skill.
A doc-sync pass compares core files like README.md, CLAUDE.md, and DEPLOY.md against actual code and configuration to surface drift. It proposes surgical edits for your approval before applying any changes to the repository.
Documentation drift happens when files like README.md or .env.example become outdated relative to the actual codebase. You need a doc-sync pass when verifying accuracy and reconciling stale entries with current configuration.
Trigger an audit pass that walks through README, CLAUDE.md, DEPLOY.md, and .env.example files to identify outdated information. It proposes targeted edits that align documentation with the actual state of the code.
Yes, the doc-sync process proposes surgical edits only after user approval. It reads and compares listed docs, tracks drift across core files and skill entries, and waits for your review before applying changes to the repository.
Yes, the audit targets a defined scope including task-rules, PHASES, ROADMAP, .claude/ directory contents, and skill files. It walks every core doc and skill entry to flag what has drifted from the actual code and configuration state.
Run a routine doc-sync session that audits README, CLAUDE.md, DEPLOY.md, and skill files against the codebase. This surfaces drift and proposes targeted edits to keep documentation accurate and synchronized with reality.
loriensleafsSynchronize CLAUDE.md navigation indexes and README.md architecture docs across a repository.
AstrumonAudit git history and map changed files to Notion documentation zones.
skyasu2Analyze post-commit validation results to generate a prioritized remediation plan.
tomique34Generate Markdown API documentation from OpenAPI specs, Python docstrings, and JSDoc/TSDoc comments.
