Review and ship

Trigger

Workflow

1. Gather context: diff against base branch, uncommitted changes, recent commits, changed files, and user intent from recent relevant chats if useful.
2. Run targeted tests for changed behavior. If no focused tests exist, decide whether to add them or document the gap.
3. Review for correctness, regressions, security, and intent fit. Use parallel subagents for larger diffs.
4. Fix critical issues before finalizing and re-run affected tests.
5. Commit selective files with a concise message.
6. Push branch and open or update a PR.

Suggested Checks

git fetch origin main
git diff origin/main...HEAD
git status
gh pr checks --json name,bucket,state,workflow,link

Guardrails

• Prioritize correctness, security, and regressions over style-only comments.
• Keep commits focused and avoid unrelated file changes.
• If pre-commit checks fail, fix the issues rather than bypassing hooks.
• Use

  gh pr checks

  instead of GitHub Actions-only commands when judging PR readiness.

Output

• Findings summary (critical, warning, note)
• Tests run and outcomes
• PR URL