Doc architecture
Skill justnau1020/claude-os/skills/development/doc-architecture
An operating system for Claude Code. Skills, hooks (MCR), and a lean-context framework for smarter AI coding sessions.
npx -y skills add justnau1020/claude-os --skill doc-architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Update architecture documentation after code changes to keep docs in sync with reality. Use when structural changes have been made and documentation needs updating.
SKILL.md
1.3 KB, as published. Nobody here has run it
Update Architecture Documentation
Update the project's architecture documentation to reflect recent code changes.
Steps
1. Review recent changes
git diff HEAD~5 --stat
git log --oneline -10
2. Read current architecture doc
Read the architecture documentation in full. Common locations:
docs/ARCHITECTURE.mddocs/architecture/ARCHITECTURE.md
3. Identify gaps
Compare the code changes against the architecture doc:
- Are new modules documented?
- Are changed interfaces reflected?
- Are removed features cleaned up?
- Are new invariants captured?
- Are new dependencies mentioned?
4. Update the doc
Make targeted updates to the architecture documentation:
- Add sections for new components
- Update descriptions for changed components
- Remove references to deleted components
- Keep the existing structure and tone
5. Verify accuracy
Cross-reference updated doc against actual code to ensure accuracy. The architecture doc is the source of truth -- it must be correct.