shepherd-review

# /shepherd-review — Quality Gate Before Pushing A mandatory quality check before any bug fix is pushed. Ensures minimal, focused changes with proper evidence. **Audience:** Developers who fixed a bug and want to verify before creating a PR. Also useful for PMs reviewing a developer's proposed fix. ## Workflow ### 1. Load Configuration Read `.claude/triage.config.yaml` for: - `review.max_line_diff` — flag if net lines exceed this - `review.tech_stack_rules` — project-specific checks - `review.require_evidence` — whether before/after evidence is required ### 2. Verify Active Session Check for an active branch (not main/master): - If on main: "No active fix branch. Run /shepherd-start {TICKET-ID} first." - Read the ticket ID from the branch name (expects: `fix/{TICKET-ID}-{slug}`) ### 3. Analyze the Diff Run `git diff main...HEAD` to see all changes in this branch. #### Check 1: Subtraction Check Count net lines added vs. removed. If net additions > `review.max_line_diff`: ``` "This fix adds {net} net lines (threshold: {max_line_diff})." "Bug fixes should ideally subtract code or be minimal. Justify each addition." ``` Verdict: WARN (not blocking, but requires justification) #### Check 2: Scope Check List all modified files. For each file: - Is it directly related to the bug being fixed? - Is it a shared/common component (used by many features)? If shared component modified: ``` "Shared component modified: {file}" "This component is used by {count} other features. C...