Update project documentation to reflect the current codebase state.
npx skills add https://github.com/Cygnusfear/claude-stuff --skill update-docs
Please help me install this Agent Skill. Skill: update-docs Source: https://github.com/Cygnusfear/claude-stuff/tree/main/skills/update-docs Command: npx skills add https://github.com/Cygnusfear/claude-stuff --skill update-docs
Outdated or inaccurate documentation leads to confusion, wasted time, and errors for developers and stakeholders. This skill automates the systematic review and update of all project documentation, ensuring it always reflects the current codebase state.
.plans, CLAUDE.md, docs, and .tasks files for accuracy and completeness.✅ Done, 📋 Todo, or ⚠️ Obsolete.find . -name ".md" -not -path "/node_modules/*"
git log --follow --pretty=format:"%ad %s" --date=short -- .plans/
High-intent search queries and answers about installing and using this skill.
Documentation drift occurs when code changes aren't reflected in docs. This skill audits `.plans`, `CLAUDE.md`, architecture docs, and `.tasks` files against your current codebase, identifying what's outdated and marking plan items as Done, Todo, or Obsolete to ensure accuracy.
Yes. This skill systematically reviews all project documentation files, analyzes git changes since the last update, and automatically flags sections requiring refresh—ideal after refactors or feature releases to audit related docs end-to-end.
The skill scans `.plans`, `CLAUDE.md`, `docs`, and `.tasks` files. It uses git history to identify which docs need attention based on recent code changes, then validates plan status tracking against the current implementation state.
Before updating documentation, the skill requires mandatory Oracle consultation to preserve critical knowledge, then validates all changes against your current codebase state using git-based change analysis to ensure updates reflect reality.
This skill performs comprehensive document review by systematically checking all `.md`, `.plans`, and `.tasks` files, then cross-referencing git commit history to identify gaps—providing structured output marking each item's status and relevance.
Yes. The skill relies on git logs to detect code changes since the last documentation update, pinpointing which docs are affected. This enables targeted updates rather than blind full rewrites.
paxlabs-incRewrite project documentation by extracting technical specifications from source code files.
helderbertoAmend the previous commit and push changes to a remote repository.
shredbxExtract implementation patterns and story context from Git history.
pramudityadVerify tests, builds, code quality, documentation, and Git status before task completion.