Review PR

Run the full review loop. Must be run on every PR.

Phase 1 — Local review (before PR)

Run PAL MCP Server codereview tool on the diff:

• •Address any issues found
• •If fixing the current (top) commit: amend it
• •If fixing an earlier commit in the stack: create a fixup commit (git commit --fixup <sha>) then autosquash (git rebase --autosquash)

Phase 2 — Submit PR

1. •

   Submit via Graphite:

   bash

   gt submit
   

2. •

   After submit, update the PR body with a proper summary and issue link. Extract the issue number from the commit message (feat(#N):) or branch name (feat/sass-lint-N-...):

   bash

   gh pr edit <number> --title "<commit title>" --body "$(cat <<'EOF'
   ## Summary
   <bullet points describing the change>
   
   Closes #N
   
   ## Test plan
   - [x] `pnpm check` passes
   - [x] <key test scenarios>
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   EOF
   )"
   

3. •

   Verify the PR body is set (not the bare template):

   bash

   gh pr view <number> --json body --jq '.body' | head -5
   

   If the body still shows the default template checklist, re-run the gh pr edit command above.

Phase 3 — Monitor CI

gh run list --branch <branch> --limit 1
gh run watch <run-id>

If CI fails:

gh run view <run-id> --log-failed

Fix, push, re-monitor.

Phase 4 — Read Gemini CI review

gh api repos/CauseMint/stylelint-sass/pulls/<number>/comments

The ai-review workflow always posts (either inline issues or a "no issues found" summary). Address actionable comments, push fixes if needed. Re-monitor CI if fixes were pushed (back to Phase 3).

Phase 5 — Hand off to human

All CI checks green + Gemini review addressed:

Report that the PR is ready for merge. The human merges via Graphite Web.