Synchronize documentation with code changes using MANIFEST tag indices.
npx skills add https://github.com/saxonthune/carta --skill documentation-nag
Please help me install this Agent Skill. Skill: documentation-nag Source: https://github.com/saxonthune/carta/tree/main/.claude/skills/documentation-nag Command: npx skills add https://github.com/saxonthune/carta --skill documentation-nag
It prevents documentation from drifting out of sync with the codebase after changes, so teams and AI agents can trust what the docs say.
Use the documentation-nag skill in the Carta workspace to analyze recent code changes, verify the affected .carta documentation via MANIFEST mappings, and generate precise edit instructions (including evidence and section targets) for updating stale docs.
High-intent search queries and answers about installing and using this skill.
To keep documentation synchronized with code changes, this skill performs content-based detection to identify changed packages, exports, and components, mapping them to relevant doc references via MANIFEST tag indices for accurate verification.
Verifying documentation claims against code behavior involves reading docs holistically, spot-checking corresponding code, and reconciling barrel-file export tables and MCP tool registrations to detect missing features or outdated behavior.
Mapping changed code exports to documentation sections requires reading the workspace MANIFEST tag index, which links code-change areas like new or removed hooks to the specific documentation references that must be checked.
Documentation synchronization explicitly supports barrel export reconciliation by cross-checking barrel-file export tables and MCP tool registrations against architecture and tool inventory docs, even when initial change analysis indicates no modifications.
Generating edit instructions for stale repository documentation involves structured gap reporting that provides precise section targets and evidence-backed instructions for updating outdated docs based on current code behavior.
Deterministic, evidence-based documentation reconciliation is needed in repository maintenance workflows where docs must stay accurate, requiring full-doc reading before section-level validation and content-based detection rather than relying on git history.
cipherstashSynchronize project documentation with code changes using a two-phase workflow.
NotysotyAudit codebases and docs folders to surface undocumented or outdated areas.
yamato0811Generate architecture design documents from templates into docs/architecture.md.
t6adevDetect documentation drift from git history and propose edits to project docs.
