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. ## 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 - Run `git log main..HEAD --oneline` to see all commits on this branch - Run `git diff main...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 main...HEAD` 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 (s...