address-pr-comments

Files (1)

• SKILL.md

SKILL.md (first lines)

# Addressing PR Review Comments

**Announce at start:** "I'm using the address-pr-comments skill to fetch unresolved review comments and dispatch the pr-comment-fixer subagent."

This skill is a thin driver. The heavy work — reading files and applying fixes — happens in the `pr-comment-fixer` subagent so the main session stays clean across iterative review cycles. **You never resolve threads.**

Two sources of feedback are checked on every run:

- **Inline threads** — PR review threads anchored to specific file/line positions (GraphQL `reviewThreads`). Tracked by `isResolved` + 👀 on the review comment.
- **Conversation items** — PR-level issue comments, e.g. a bot's top-level review summary (REST `issues/$PR_NUMBER/comments`). Tracked by 👀 on the issue comment (there is no `isResolved` for these).

## Where the subagent lives

- `.claude/agents/pr-comment-fixer.md`

If it is missing, run `agent-workflow-beads update` against the repo to install it.

## Prerequisites

- Working directory is the downstream repo with the PR's feature branch checked out.
- `gh` CLI is installed and authenticated (`gh auth status`).
- Working tree is clean (or any uncommitted changes are intentional).
- `gh pr view` succeeds — the branch has an open PR.

If any prerequisite fails, stop and report.

## Steps

### 1. Identify the PR, repo, and "us"

```bash
gh pr view --json number,headRefName,url,state,author -q '{number, branch: .headRefName, url, state, author: .author.login}'
gh repo view --json owner,name -q '{owner: .owner.login, name}'
```

Capture `OWNER`, `REPO`, `PR_NUMBER`, and `AUTHOR_LOGIN` (the PR author — this is "us" for the purpose of detecting our own replies). If `state != OPEN`, stop.

### 2. Fetch all actionable review feedback

Run both fetches. Combine results into a single actionable list.

#### 2a. Inline review threads (GraphQL)

```bash
gh api graphql -f query='
  query($owner: String!, $repo: String!, $pr: Int!) {
    repository(owner: $owner, name: $repo) {
      pullRequest(number: $pr) {
        reviewThreads(first: 100) {
          nodes {
            id
            isResolved
            isOutdated
            path
            line
            comments(first: 50) {
              nodes {
                databaseId
                author { login }
                body
                path
                line
                diffHunk
                url
                createdAt
                reactions(first: 20, content: EYES) {
                  nodes { user { login } }
                }
              }
            }
          }
        }
      }
    }
  }' -F owner="$OWNER" -F repo="$REPO" -F pr="$PR_NUMBER"
```

A thread is **actionable** when both hold:

1. `isResolved == false`
2. The latest reviewer comment (latest `comments.nodes[]` where `author.login != AUTHOR_LOGIN`) does **not** have a 👀 reaction from `AUTHOR_LOGIN`

Keep `isOutdated` threads if they pass both filters.

#### 2b. Conversation comments (REST)

```bash
gh api "repos/$OWNER/$REPO/issues/$PR_NUMBER/comments" --paginate
```

For each comment where `author.login != AUTHOR_LOGIN`, fetch its 👀 reactions:

```bash
gh api "repos/$OWNER/$REPO/issues/comments/$COMMENT_ID/reactions?content=eyes"
```

A conversation comment is **actionable** when the 👀 list contains no entry with `user.login == AUTHOR_LOGIN`.

Skip comments authored by `AUTHOR_LOGIN` (those are our own prior replies, not reviewer asks).

#### Combined filter

If zero actionable items remain across both sources, report "No actionable unresolved feedback (all already 👀'd or resolved)" and stop.

### 3. Build the brief and dispatch the subagent

Transform the results into the brief schema the subagent expects. Every item has a `kind` field.

**Inline thread item:**

- `kind: "inline"`
- `thread_id` — the GraphQL `id`
- `root_comment_id` — `comments.nodes[0].databaseId`
- `latest_reviewer_comment_id` — `databaseId` of the most recent comment where `author.login != AUTHOR_LOGIN`
- `path`, `line`, `is_outdated`
- `comments[]` — all messages oldest-first, each with `author.login` and `body`
- `diff_hunk`, `url`

**Conversation item:**

From jsiovn/agent-workflow-beads, MIT.

More from jsiovn/agent-workflow-beads