maintaining-docs-after-changes
Provides a two-phase workflow for keeping project documentation synchronized with code changes. Analyzes git diffs to identify documentation gaps, then updates README, CLAUDE.md, and other docs. Includes checklists, common mistakes to avoid, and explicit trigger conditions for when to use it.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install cipherstash-cipherpowers-maintaining-docs-after-changes
Repository
Skill path: plugin/skills/maintaining-docs-after-changes
Provides a two-phase workflow for keeping project documentation synchronized with code changes. Analyzes git diffs to identify documentation gaps, then updates README, CLAUDE.md, and other docs. Includes checklists, common mistakes to avoid, and explicit trigger conditions for when to use it.
Open repositoryBest for
Primary workflow: Write Technical Docs.
Technical facets: Tech Writer, Full Stack, Integration.
Target audience: Documentation teams looking for install-ready agent workflows..
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: cipherstash.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install maintaining-docs-after-changes into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/cipherstash/cipherpowers before adding maintaining-docs-after-changes to shared team environments
- Use maintaining-docs-after-changes for documentation workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.