codument: Skill for Claude Code

Review Work

Use this after a planned step has been implemented and before committing.

If this is the session's first workflow action, run the compatibility check from work-step before lifecycle commands. The actual executable must expose work and verify; repair a mismatch instead of substituting older commands or manual checkpoints.

For compact dead-code cleanup, use the same generated worksheet and independent reviewer. Check the unused-code evidence against exports, dynamic loading, framework entry points and side effects; deletion is never automatically trivial. Do not demand a second plan or a separate review bundle when the worksheet already supplies the reviewed boundary. Historical paths inside the plan remain valid scope; durable Key files and registry pointers must describe what remains.

Review Order

1. Read codument work status --json and its approved plan step. After final compaction, use the tracked contract and final-delivery binding in docs/.approvals.json; the pending-plans recovery copy supplies working context only. Inspect the compacted doc in the staged boundary as usual.
2. Inspect git diff --cached; that exact staged boundary, not the whole dirty worktree, is the review subject.
3. Run codument verify once. Read the generated reviewPolicy.minimum and reasons; it writes .codument/review-worksheet.json when required focused or adversarial review lacks current coverage.
4. Diagnose routine test, mapping or documentation failures and correct the cause within the approved contract. Batch missing source registration through codument map materialize <files...>, inspect any partial failure and retry after correcting it, then restage and rerun the affected checks and codument verify. The staged boundary checks ownership and doc sync together; do not repeat per-file ownership queries or add mirror prose merely to make it green. Ask the human only when repair needs an unapproved decision, external input or a genuinely irreversible action.
5. Compare the promised outcome and acceptance criteria with the evidence actually obtained at the relevant user or integration boundary. Name untested assumptions and substitutes; missing required evidence remains a blocker unless the user explicitly changes acceptance. Review the exact staged diff, mapped invariants, tests and generated reviewContext when present with the effort below.
6. When a worksheet is required, complete only its top-level invariantsChecked, findings, and signer fields. Do not alter generated context. Run the exact printed codument verify --record .codument/review-worksheet.json command; it records and verifies the same staged boundary in that invocation.
7. Fix safe, obvious findings that follow the approved contract, restage, and return to step 3. Findings involving public interfaces, privacy, security, migrations, data loss, deletions or dependencies receive stronger review; an obvious contracted fix does not require renewed human approval merely for touching that boundary. Pause for unapproved judgment calls, changed promises or constraints, external input or a genuinely irreversible action. A changed boundary invalidates its earlier review automatically; gated mode still waits for the user's findings decision.
8. When codument verify passes, run codument work finish to preserve verified readiness, then continue to commit-work without a routine prompt. If the user prohibited commits, stop with ready work and the pending commit visible. The exact receipt lets the hook confirm unchanged staged bytes. Gated and single-step requests retain their limits.
9. If review pauses or the user redirects work, preserve the plan path, step, next gate, unresolved finding or failure, and resume condition in the plan's Resume checkpoint (in its recovery copy after final-step compaction). Recheck the staged boundary on return; a changed boundary invalidates earlier review. If fixes restore delivery scaffolding, recompact and restage it before recording the final review.