Claude-skill-registry doc-update
Updates documentation after code changes to keep docs in sync with code reality. Use AFTER implementation is complete. Covers feature docs, workflow docs, and index files.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/doc-update" ~/.claude/skills/majiayu000-claude-skill-registry-doc-update && rm -rf "$T"
manifest:
skills/data/doc-update/SKILL.mdsource content
Doc Update
Keep documentation evergreen by updating immediately after code changes.
When to Use
- After completing any code change
- After fixing a bug or adding a feature
- Before running
/handoff - When
identifies stale docs/drift-check
Hierarchy
Updates flow from specific to general:
- Feature Docs →
docs/features/{feature}.md - Workflow Docs →
docs/workflows/{role}-workflows.md - Index Files → FEATURE_INDEX.md, WORKFLOW_INDEX.md
- Architecture Docs →
(if patterns changed)docs/engine/*.md
Quick Reference
| Files Changed | Update |
|---|---|
| Feature doc → Server Actions |
| Feature doc → User Surfaces |
| Feature doc + Component Index |
| Feature doc → Data Model + prod SQL |
| AI context docs + feature docs |
Feature Doc Sections to Update
- User Surfaces: Routes, UI elements
- Data Model: Tables, columns, relationships
- Server Actions: Action name, purpose, tables, auth
- Permissions: RLS policies, admin client usage
- Invariants: Add newly discovered rules
- Testing Checklist: Update verification steps
Output
## Doc Update Complete ### Updated | Doc | Sections | |-----|----------| | [feature].md | User Surfaces, Data Model | ### Production SQL - Provided: [Yes/No] ### Verification Run `/drift-check` to confirm no remaining drift.
Related
- Section templates: See reference/section-templates.md
- Common patterns: See reference/update-patterns.md
- Next step:
/drift-check