PR Resolve Workflow

When activated, execute this workflow to systematically address all PR review comments:

Steps

1. •

   Determine Issue ID: Extract the issue number from the branch name (e.g., BT-10 from BT-10-implement-erlang-codegen). If not in branch name, try:

   a. Worktree name: If in a git worktree with a name matching BT-{number}:

   bash

   # Check if this is a worktree
   git rev-parse --git-dir 2>/dev/null | grep -q "worktrees"
   
   # Extract issue ID from directory name
   basename "$(pwd)" | grep -oE '^BT-[0-9]+'
   

   Example: /workspaces/BT-34 → issue BT-34

2. •

   Get PR review comments: Fetch all unresolved review comments from the active PR:

   bash

   gh api repos/{owner}/{repo}/pulls/{pr}/comments --jq '.[] | select(.in_reply_to_id == null) | {id, path, body}'
   

3. •

   Analyze and plan: For each review comment:

   • •Understand what the reviewer is asking for
   • •Determine if it needs a code fix, documentation, Linear issue, or just clarification
   • •Create a todo list with all items to address
4. •

   Run tests first: Verify current state passes all checks:

   bash

   just ci
   

   This runs all CI checks (build, clippy, fmt-check, test, test-e2e).

5. •

   Write tests first (TDD): For each code fix needed:

   • •Write a failing test that demonstrates the bug or missing behavior
   • •Run the test to confirm it fails as expected
   • •This ensures the fix is verifiable and prevents regressions
6. •

   Address each comment: For each item in the plan:

   • •Make the necessary code changes to make the test pass
   • •Run tests after each significant change to catch regressions early
   • •If a comment requires a follow-up Linear issue (e.g., "TODO for later"):
     • •Create the Linear issue with full context
     • •Add a TODO comment in the code referencing the issue number
   • •Mark the todo item complete
7. •

   Run full test suite: After all changes:

   bash

   just ci
   

8. •

   Commit changes: Stage and commit with a descriptive message (using issue ID from step 1):

   bash

   git add -A
   git commit -m "fix: address PR review comments BT-{number}
   
   - Summary of each fix
   - Reference any Linear issues created"
   

9. •

   Push changes:

   bash

   git push
   

10. •

    Reply to each comment: For every review comment that was addressed, add a reply explaining what was done:

gh api repos/{owner}/{repo}/pulls/{pr}/comments/{comment_id}/replies -f body="<explanation of fix, commit hash, any Linear issues created>"

Include:

• •Commit hash where the fix was made
• •Brief description of the change
• •Links to any Linear issues created for follow-up work

1. •

   Report summary: Provide a summary table of all comments and how they were resolved.

2. •

   Auto-chain to done: If all review comments have been successfully resolved (no failures, no pending issues), automatically activate the done skill:

   • •Inform the user that all PR comments have been addressed
   • •Activate the done skill without waiting for user confirmation

   If there are any issues or manual steps needed, report them and wait for user input instead.