Finish Pr

1. Confirm branch and cleanliness:

git status --short --branch

2. Sync with main (choose one strategy used by the repo):

git fetch origin
git merge origin/main

If conflicts appear: resolve, run checks, commit conflict resolution.

3. Run local gates with shortest feedback first:

bun run type-check
bun run lint
bun run static-check

4. Check PR CI status:

gh pr checks <PR_NUMBER>

If failing, fix the first root cause, then re-run local gates.

5. Read unresolved CodeRabbit threads safely:

gh api graphql -f query='
query {
  repository(owner:"<OWNER>", name:"<REPO>") {
    pullRequest(number:<PR_NUMBER>) {
      reviewThreads(first:100) {
        nodes {
          id
          isResolved
          comments(first:20) {
            nodes { body url author { login } }
          }
        }
      }
    }
  }
}
' --jq '.data.repository.pullRequest.reviewThreads.nodes
  | map(select(.isResolved==false))
  | map({id, comments:[.comments.nodes[] | {author:.author.login, url, body}]})'

6. For each unresolved item:

• Fix code if valid.
• If disagree, reply with concrete reasoning and evidence.
• Resolve the thread only after fix/reasoning is in place.
• If a CodeRabbit comment is fixed, you must mark that review thread as resolved.

7. Re-run checks after fixes:

bun run static-check
gh pr checks <PR_NUMBER>

8. Push branch:

git push

9. Final verify:

• gh pr checks <PR_NUMBER> shows all required checks passing.
• No unresolved CodeRabbit review threads remain.

Fast Triage Order

1. Type-check failures
2. Lint/format failures
3. Test failures
4. CodeRabbit review threads
5. Re-run full checks once at the end

Done Criteria

1. Branch is pushed.
2. Required CI checks are green.
3. CodeRabbit unresolved thread count is zero (or documented with explicit, accepted disagreement).