dev-workflow:address-pr-comments

Address PR Comments

Role: Address review feedback on the current PR — read, implement, and respond

SCOPE BOUNDARY: This skill never creates PM stories, tickets, issues, or subtasks — the Story Creation Gate in skills/shared/standards.md applies.

Read skills/shared/standards.md — these mandatory rules govern this entire session.

Compact the conversation before continuing — you are about to iterate on existing work.

---

Step 1: Identify the PR

If no PR number is provided in context:

gh pr status --json currentBranch

Use the current branch's open PR. If no PR is open, ask the user for the PR number.

---

Step 2: Load New Feedback

Fetch all comment types since the last commit. Use the actual PR number in every command.

Conversation comments:

gh api repos/{owner}/{repo}/issues/{PR_NUMBER}/comments

Inline file comments:

gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/comments

Reviews (state + body):

gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/reviews

Filter to comments created or updated after the last commit timestamp:

git log -1 --format=%cI

Deduplicate: if an inline comment is also referenced in a review body, address it once.

---

Step 3: Summarize Required Changes

Before writing any code, list every actionable item as a numbered checklist:

## Changes Required

1. [Author @foo, file.ts:42] — [what they asked for]
2. [Author @bar, review body] — [what they asked for]

If no actionable feedback is found, inform the user and stop.

---

Step 4: Implement Changes

Address each item from the checklist:

• Apply the full RED-GREEN-REFACTOR cycle for code changes:

  Invoke Skill: superpowers:test-driven-development

• Address items in checklist order — do not skip or defer
• Do not change anything outside the scope of reviewer feedback
• Commit frequently with descriptive messages referencing the item being addressed

---

Step 5: Verify

Invoke Skill: superpowers:verification-before-completion

Verify with fresh execution:

• All tests pass (run the full suite now)
• Each checklist item from Step 3 has been addressed
• Code is pushed to remote

---

Step 5.5: Functional Verification in Dev Environment

After unit/integration tests pass, verify the fixes work in a running environment. Loop until certain.

Deploy:

Check ~/.claude/dev-workflow/config.json for deploy_command.

• If deploy_command is configured: Deploy the branch to dev — follow the same deployment procedure as dev-workflow:test-pr Phase 3 (GitHub Actions, shell command, or other pattern).
• If not configured: Run the service locally. Start it using whatever mechanism the project provides (Makefile, npm scripts, etc.).

Test:

For each item from the Step 3 checklist, design and execute a focused test scenario:

1. Document what you're doing and the expected outcome
2. Execute with fresh commands — no assumptions from prior runs
3. Collect evidence: logs, API responses, CLI output, screenshots
4. Record PASS or FAIL with specific details

Apply the accountability rules from dev-workflow:test-pr: if you see an error, it is a failure — do not rationalize it away.

Loop:

• If any test fails → fix the issue, commit, push, re-deploy, re-test
• Continue until ALL addressed items pass functional testing
• Only proceed to Step 6 when you are certain every fix works correctly in the running environment

---

Step 6: Reply to PR

6a: Reply to Inline Comments Directly

For each inline file comment addressed in Step 4, post a direct reply on that comment thread explaining what was changed:

gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/comments/{COMMENT_ID}/replies -f body="..."

Reply format: one concise sentence stating what was done (e.g., "Fixed — switched to parseISO() at utils.ts:47."). Do not repeat the reviewer's request back to them.

If you deviated from what the reviewer asked on a specific comment, explain why in the reply to that comment.

6b: Post Summary Comment

Post a summary comment on the PR covering all changes. Call out any deviations not already explained in inline replies.

Comment format:

## Changes Addressed

1. [Item 1] — [what was changed and where: file.ts:42]
2. [Item 2] — [what was changed and where]

## Deviations
[Omit section entirely if none. Otherwise explain each deviation and reasoning.]

gh pr comment {PR_NUMBER} --body "..."