Drift Check

Drift Check

Pre-PR deviation check against the project spec. Run this before /create-pr to verify alignment between implementation and documentation.

Reference: See ~/.claude/docs/prd-workflow/spec-driven-development.md §2–§4 for the deviation threshold, workflow, and checkpoint cadence that this skill operationalizes.

Not the same as /code-review — that inspects the diff for correctness bugs and cleanups; this checks the diff against the spec and docs for deviations. They run at the same pre-PR moment and complement each other.

Your task

Perform a lightweight, advisory review of the current branch's changes against the project's spec and living documents. This is a read-only check — do not modify any files.

Step 1: Identify scope

• Determine the default branch first — don't assume main. Run git rev-parse --abbrev-ref origin/HEAD; it prints e.g. origin/main or origin/master, and the part after origin/ is the base branch for the commands below. If it errors (no origin/HEAD set locally), fall back to git remote show origin (read its "HEAD branch:" line) or default to main. Use this detected base wherever <base> appears below. (Run the detection as a plain command and substitute the result literally — don't wrap it in $(...), which triggers a permission prompt.)
• Run git log <base>..HEAD --oneline to see all commits on this branch
• Run git diff <base>...HEAD --stat to see all files changed
• Determine which feature area this work relates to (from branch name, commit messages, or changed files)

Step 2: Identify the relevant spec

• Check for docs/prd/ROADMAP.md — if it exists, identify which phase or item this work relates to
• Check for docs/prd/ files that cover the feature area
• Check for living documents (domain model, integration guides, runbooks) that describe the current state of the affected models or features
• If no spec exists for this work (e.g., a bug fix or chore with no PRD entry), note that and skip to Step 4

Step 3: Scan for deviation signals

Review git diff <base>...HEAD (the base branch detected in Step 1) for changes that cross the deviation threshold:

Flag if present:

• New or removed database migrations (new models, columns, associations)
• Changes to model validations or lifecycle (status enums, state transitions)
• New or changed URL patterns (routes file changes)
• Changes to authorization rules (policy files)
• New or altered mailer actions or notification triggers
• API contract changes (new endpoints, changed request/response shapes)

For each flagged change, check whether the relevant spec or living document already describes it. If it does, no action needed. If it doesn't, this is a potential deviation.