name	address-pr-review
description	Look at the pull request review comments and address any issues raised.
disable-model-invocation	true
context	fork
allowed-tools	Bash(bash ~/.claude/skills/address-pr-review/), Bash(bash .claude/skills/address-pr-review/)

First, run git branch --show-current to retrieve the current branch. Do not trust branch/git status information present in the conversation context as it may be stale.

Step 1: Fetch unresolved review threads and CI status

Run both helper scripts located in this skill's directory (the directory containing this SKILL.md):

bash <skill-directory>/get-unresolved-threads.sh

bash <skill-directory>/get-failing-ci.sh

The first returns a JSON array of unresolved threads. Each thread has:

id — thread ID (needed to reply)
path — file path
line / startLine — line numbers in the diff
isOutdated — whether the diff has changed since the comment
comments.nodes[] — the comment thread (first = original comment, rest = replies), each with author.login, body, and url

The second checks CI status and outputs failure details if any jobs failed (exit code 1 = failures, 0 = all passed).

If there are no unresolved threads and CI is green, stop here.

Step 2: Address each issue

If there are many items, create one task per item to keep things organized.

For each unresolved review thread:

Read the comment thread to understand the issue
Determine if a code change is needed, or if no change is needed (e.g. the comment is invalid or the suggestion is not appropriate)
If a change is needed, make the necessary code changes

For each CI failure:

Read the failure output to understand what broke
Fix the code or tests to make CI pass

Step 3: Commit and push changes

After addressing all review comments and CI failures, commit your changes and push.

Step 4: Reply to each review thread

After addressing each comment, reply using the helper script:

bash <skill-directory>/reply-to-thread.sh "<thread_id>" "<body>" [--resolve]

If the code was fixed as mentioned in the thread, reply with simply: "Fixed as suggested." and pass --resolve to mark the thread as resolved.
If no change was applied, briefly explain why and keep the thread unresolved (omit --resolve) so the reviewer can reply if they disagree.
Don't be unnecessarily verbose.

name	address-pr-review
description	Look at the pull request review comments and address any issues raised.
disable-model-invocation	true
context	fork
allowed-tools	Bash(bash ~/.claude/skills/address-pr-review/), Bash(bash .claude/skills/address-pr-review/)

First, run git branch --show-current to retrieve the current branch. Do not trust branch/git status information present in the conversation context as it may be stale.

Step 1: Fetch unresolved review threads and CI status

Run both helper scripts located in this skill's directory (the directory containing this SKILL.md):

bash <skill-directory>/get-unresolved-threads.sh

bash <skill-directory>/get-failing-ci.sh

The first returns a JSON array of unresolved threads. Each thread has:

id — thread ID (needed to reply)
path — file path
line / startLine — line numbers in the diff
isOutdated — whether the diff has changed since the comment
comments.nodes[] — the comment thread (first = original comment, rest = replies), each with author.login, body, and url

The second checks CI status and outputs failure details if any jobs failed (exit code 1 = failures, 0 = all passed).

If there are no unresolved threads and CI is green, stop here.

Step 2: Address each issue

If there are many items, create one task per item to keep things organized.

For each unresolved review thread:

Read the comment thread to understand the issue
Determine if a code change is needed, or if no change is needed (e.g. the comment is invalid or the suggestion is not appropriate)
If a change is needed, make the necessary code changes

For each CI failure:

Read the failure output to understand what broke
Fix the code or tests to make CI pass

Step 3: Commit and push changes

After addressing all review comments and CI failures, commit your changes and push.

Step 4: Reply to each review thread

After addressing each comment, reply using the helper script:

bash <skill-directory>/reply-to-thread.sh "<thread_id>" "<body>" [--resolve]

If the code was fixed as mentioned in the thread, reply with simply: "Fixed as suggested." and pass --resolve to mark the thread as resolved.
If no change was applied, briefly explain why and keep the thread unresolved (omit --resolve) so the reviewer can reply if they disagree.
Don't be unnecessarily verbose.

address-pr-review

Step 1: Fetch unresolved review threads and CI status

Step 2: Address each issue

Step 3: Commit and push changes

Step 4: Reply to each review thread

Step 1: Fetch unresolved review threads and CI status

Step 2: Address each issue

Step 3: Commit and push changes

Step 4: Reply to each review thread