From review-doc-commit
Review, document, and commit. Use proactively when user asks to commit. Hard gate: no commit until review is clean.
How this skill is triggered — by the user, by Claude, or both
Slash command
/review-doc-commit:review-doc-commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review, document, and commit workflow. Use dedicated subagents for review, documentation, and commit phases.
Review, document, and commit workflow. Use dedicated subagents for review, documentation, and commit phases.
Execution model:
Parse the user's request:
/review-doc-commit with no path → all unstaged/staged changes/review-doc-commit <message or path> → scope to the specified path or use as contextRun git status and git diff (staged + unstaged) to identify all changed files. If a path scope was given, filter to only changes under that path.
Output contract from Scope phase:
Review and update documentation thoroughly so it reflects the latest changes. This includes inline docs and top-level/project docs.
Coverage checklist:
CLAUDE.md / AGENTS.md (see nested structure below)README.md (root and impacted module-level READMEs)docs/, architecture notes, runbooks, examples, changelogs)Context is progressively revealed through a hierarchy of CLAUDE.md files. Each level adds module-specific guidance without repeating what parent docs already cover:
CLAUDE.md — overall architecture, tech stack, build/test commands, project-wide conventionsCLAUDE.md — the module's purpose, its conventions, non-obvious design decisions, and how to work with itWhen reviewing or documenting a file, walk up from the file's directory to the repo root and read every CLAUDE.md encountered along the way. The union of these files provides the full context for that file.
AGENTS.md is a mirror of CLAUDE.md. Both names should resolve to the same content. When creating or discovering guidance docs:
CLAUDE.md exists, create a symlink: ln -s CLAUDE.md AGENTS.mdAGENTS.md exists, create a symlink: ln -s AGENTS.md CLAUDE.mdCLAUDE.md exists.CLAUDE.md, create one describing the module's purpose and conventions.AGENTS.md symlink exists alongside every CLAUDE.md (and vice versa).Rules for documentation content:
Output contract from Documentation Subagent:
Phase 2 must complete before Phase 3 starts. This ensures reviewers can verify that documentation updates are consistent with code changes.
Spawn two review subagents in parallel, each with a distinct perspective. A common failure mode is reviewing changes in isolation — one agent focuses narrowly on the changed files while missing how those changes interact with the rest of the project. These two agents address that by splitting the review into complementary scopes.
Focus: the changed code itself.
CLAUDE.md by walking up from each changed file's directory to the repo root.CLAUDE.md/AGENTS.md guidance.Focus: how the changes fit into the broader project.
After both subagents complete:
If any issues are found:
Skip deep quality review for binary/generated files.
Commit only after Phase 2 documentation updates and Phase 3 review are both complete and clean. Group changes into topical commits. Never combine unrelated changes.
<type>: <concise description>
<optional body explaining why, not what>
Co-Authored-By: Claude <model> <[email protected]>
Types: feat, fix, refactor, docs, test, chore
For each topic group:
git add <specific files>)git status after each commitdocs: update project documentationnpx claudepluginhub fuzhiyu/agentcontract --plugin review-doc-commitGuides git commit workflow: analyzes staged files, generates conventional messages (feat/fix/etc.), updates README for features/setup changes, ignores unstaged.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.