Stats
Actions
Tags
How this skill is triggered — by the user, by Claude, or both
Slash command
/documentation:update-project-docsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Update all three project-level documentation files in a single pass: `README.md`, `CLAUDE.md`, and `llms.txt`.
Update all three project-level documentation files in a single pass: README.md, CLAUDE.md, and llms.txt.
Run /update-readme: Invoke the update-readme skill to analyze the codebase and update README.md.
Run /revise-claude-md: Invoke the revise-claude-md skill to update CLAUDE.md with learnings from the
current session and codebase state.
Run /generate-llms-txt: Invoke the generate-llms-txt skill to generate or update llms.txt (and
llms-full.txt if the project is small enough).
Report: Summarize what changed across all three files. List each file and whether it was created, updated, or left unchanged.
README.md and CLAUDE.md are inputs to llms.txt generation, so they
should be current before that step runs.npx claudepluginhub mattbobambrose/mattbobambrose-claude-skills --plugin documentationUpdates, refreshes, optimizes, and cleans up CLAUDE.md by exploring codebase, removing stale content, and restructuring for scannability. Use when docs are out of sync.
Analyzes codebase structure and updates README.md and docs/ directories to reflect current code state, including changes since last doc update. Triggers on 'update docs' or staleness checks.
Creates or updates CLAUDE.md following best practices: WHAT/WHY/HOW structure, 30-300 line limits, progressive disclosure with doc references, pointers over copies, verified commands.