DI

divecode-pr-watch

Monitor PR status and automate merging or feedback loops based on live results.

Install

mkdir -p .claude/skills/divecode-pr-watch && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11816" && unzip -o skill.zip -d .claude/skills/divecode-pr-watch && rm skill.zip

Installs to .claude/skills/divecode-pr-watch

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Watch a PR — auto-respond to comments and CI failures. Uses bin/divecode-pr-watch which polls via gh and emits a routing decision (status + route). 6-status / 7-route routing per agent-flow: green→merge, has_comments→fix-loop, ci_failed→fix-loop, pending→block, closed→block, merged→cleanup, error→block. Use after /divecode-push-pr, before /divecode-merge.
357 charsno explicit “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Fetch the live status of a Pull Request
  • Decide the next route based on PR status
  • Invoke `/divecode-merge` for `green` status
  • Invoke `/divecode-fix-loop` for `has_comments` or `ci_failed`
  • Suggest re-invocation for `pending` status
  • Record each poll/action in `pr-watch.md`

How it works

The skill fetches the live status of a Pull Request, uses a deterministic routing table to decide the next action, and records the process.

Inputs & outputs

You give it
Pull Request number
You get back
PR status, determined route, and recorded action in `pr-watch.md`

When to use divecode-pr-watch

  • Watch a pull request status
  • Auto-respond to CI failures
  • Automate PR merging

About this skill

divecode-pr-watch — status-driven routing

You are running divecode-pr-watch. Read the PR's live status, decide the next route per agent-flow's 6-status contract.

Iron Laws

  1. Status is computed, not assumed. Always actually fetch the PR.
  2. One status → one route. No "maybe try X then Y" — the routing table is deterministic.
  3. Block ≠ fail. Pending CI is not a failure; just don't merge yet.
  4. Closed (not merged) requires user input. Never auto-cleanup a closed-without-merge PR.

Preamble

PROJ_DIR="${DIVECODE_PROJECT_DIR:-$PWD}"
DIVECODE_HOME="${DIVECODE_HOME:-$HOME/.divecode}"
[ -x "$DIVECODE_HOME/bin/divecode-pr-watch" ] || DIVECODE_HOME="$HOME/Trappist/divecode"

# Find PR number from push-pr.md
PR=$(grep -E '^url:' "$PROJ_DIR/divecode/push-pr.md" 2>/dev/null | head -1 | grep -oE '/pull/[0-9]+' | grep -oE '[0-9]+')
[ -z "$PR" ] && { echo "could not find PR in divecode/push-pr.md"; exit 1; }
echo "PR: $PR"

Workflow

Step 1 — Fetch + route

bash "$DIVECODE_HOME/bin/divecode-pr-watch" "$PR" > "$PROJ_DIR/divecode/pr-watch.md"
cat "$PROJ_DIR/divecode/pr-watch.md"

Routing table (matches agent-flow exactly):

statusrouteaction
greenmergeinvoke /divecode-merge
has_commentsfix-loopinvoke /divecode-fix-loop with PR comments converted into must-fix items
ci_failedfix-loopinvoke /divecode-fix-loop; reproduce the failure locally, fix, push
pendingblocksleep / wait — re-invoke pr-watch after ~5min
closed (not merged)blockask user before proceeding
mergedcleanupinvoke /divecode-cleanup
errorblocksurface error; do not retry until user input

Step 2 — Branch per route

Per the table. For pending, suggest the user re-invoke later or set a timer.

Step 3 — Append round entry to pr-watch.md

Each poll/action is recorded:

## Round <N> — <date>
status: <s>
route:  <r>
action: <what was done>

Done criteria

  • pr-watch.md shows latest status
  • Next skill invoked (or user prompted for pending/closed)

When not to use it

  • Assuming PR status without fetching it
  • Attempting multiple actions for a single status
  • Auto-cleaning up a PR that was closed without merging

Limitations

  • Status is computed, not assumed
  • One status leads to one route
  • Does not auto-cleanup a closed-without-merge PR

How it compares

This skill uses a fixed 6-status/7-route deterministic routing table to automate PR workflow decisions, which is more structured than manual PR monitoring.

Compared to similar skills

divecode-pr-watch side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
divecode-pr-watch (this skill)03moReviewIntermediate
fix-pr14moReviewIntermediate
resolve-checks16moReviewIntermediate
agent-github-pr-manager16moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry