address-pr-review

When to invoke

Use when: "address the review", "fix the review comments", "resolve the threads", "CI is red on the PR", "iterate on the PR", or when a shipping flow hands back a PR that has unresolved threads or failing checks.

Preamble

eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown"
_LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl"
if [ -f "$_LEARN_FILE" ]; then
  _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ')
  echo "LEARNINGS: $_LEARN_COUNT entries loaded"
  if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then
    ~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true
  fi
else
  echo "LEARNINGS: none yet"
fi

{{include lib/snippets/session-host.md}}

{{include lib/snippets/decision-brief.md}}

{{include lib/snippets/working-protocols.md}}

{{include lib/snippets/state-protocols.md}}

User-invocable

When the user types /address-pr-review, run this skill.

---

Step 1: Confirm the branch

Never trust the branch name from earlier in the conversation. Ask git:

git branch --show-current
git status --short

If the branch is the default branch (main, master), stop: there is no PR to address from there. Say which branch you are on and ask the user to check out the feature branch.

If the working tree is dirty, list the dirty files before doing anything, and keep that list. Step 5 stages only the files this round actually edited, so the list is how you tell your own edits from work that was already in the tree.

---

Step 2: Collect what is open

Run both collectors. They read the PR from the current branch on their own.

bash "${CLAUDE_SKILL_DIR}/bin/pr-threads.sh"
bash "${CLAUDE_SKILL_DIR}/bin/pr-ci-failures.sh"

pr-threads.sh prints a JSON array of unresolved review threads. Each thread carries id, path, line, isOutdated, and its comments with author, body, and url. The array is the whole list — the script pages through every thread, so a long review is not silently cut short. Exit 2 means there is no PR for this branch (stop and say so; /ship is the skill that opens one), or that a page of threads could not be fetched. On that second case nothing is printed at all: treat it as unknown, not as zero threads, and re-run.