From up-docs
Update repository documentation (README.md, docs/, CLAUDE.md) based on session changes. This skill should be used when the user runs /up-docs:repo.
How this skill is triggered — by the user, by Claude, or both
Slash command
/up-docs:repoThis 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 the active repository's documentation files to reflect work done in the current session.
Update the active repository's documentation files to reflect work done in the current session.
Gather what changed during the session:
git diff --stat HEAD~5 HEAD 2>/dev/null || git diff --stat
git log --oneline -10
Also consider the conversation history: files discussed, features implemented, bugs fixed, configuration changes made. Build a mental model of what the session accomplished.
Read the project CLAUDE.md for any ## Documentation section that specifies which files to update.
If no explicit mapping exists, discover documentation files:
# Find all markdown docs in standard locations
find . -maxdepth 1 -name "*.md" -type f
find ./docs -name "*.md" -type f 2>/dev/null
Common targets: README.md, CLAUDE.md, CHANGELOG.md, docs/*.md, and any other .md files at the project root or in docs/.
Read every candidate documentation file. For each one, determine whether the session's changes make any part of it stale or incomplete.
Evaluation criteria:
Skip files that are clearly unaffected by the session's work.
For each file that needs changes:
Do not add boilerplate, badges, or sections that the file doesn't already have. Match the document's existing conventions.
Read ${CLAUDE_PLUGIN_ROOT}/templates/summary-report.md for the output format.
Emit the summary report using the Repo layer format. Every file examined gets a row in the table, including files where no changes were needed.
npx claudepluginhub l3digitalnet/claude-code-plugins --plugin up-docsImplements two-phase workflow to analyze code changes via git diff and update project documentation. Use before merging branches, after features/bugfixes, or when docs stale.
Automates updating README.md, CHANGELOG.md, and docs folders via git diff analysis of changes since last release tag. Use for release prep, PRs, or doc 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.