precommit-evidencelisted
Install: claude install-skill Shantydotcom/northstariq-revenue-operations-intelligence
# Pre-Commit Evidence Review
The last step of a task. Establishes what changed, what proves it, and whether the work can honestly
be presented for commit approval.
**It never commits.**
Governance comes from `~/.claude/CLAUDE.md` and the repository `CLAUDE.md`; both apply throughout and
are not restated here. What follows is procedure.
## When to run it
At a task's intended stopping point — after implementation, after task-specific validation, before
asking for commit approval. Also on explicit request: *review before commit* · *is this ready?* ·
*validate what changed* · *review the diff* · *make sure nothing broke*.
This is an evidence review, not another implementation phase.
## Core principle
> **Validation is selected by what changed and what claim is being made** — never by directory
> membership, and never from a fixed checklist.
Do not run every available check. Do not skip relevant evidence because one broad check passed.
A green repository validator proves **repository invariants**. It does not prove Salesforce
behaviour, runtime behaviour, visual fidelity, business correctness or deployed state.
## Procedure
### 1 · Establish the review baseline
Determine the branch, staged state, working-tree state, which files the task authorised, which work
is pre-existing or unrelated, and which changes the task introduced.
Establish provenance from the **baseline status captured at task start**, the known task edits, the
diff content, deliberately captured hashes