Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gmickel/flow-next-resolve-pr
Resolve PR review feedback — fetch unresolved threads, triage, dispatch per-thread resolver agents, validate, commit, reply + resolve via GraphQL.
Passed 9 of 16 test cases with the skill, and 6 of 16 without it.
and 8 more in the full report
8 fixed5 passed either way6 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have 12 independent review comment threads touching non-overlapping files ready for parallel dispatch. What is the maximum number of resolver units that can be dispatched per parallel wave?
| Checked | Without skill | With skill |
|---|---|---|
| The output caps the parallel batch size at 4 units per wave | Missed | Passed |
The instructions your model reads when the skill loads.
Read workflow.md for full phase-by-phase execution. Read cluster-analysis.md for cross-invocation clustering rules.
Coordinate resolution of unresolved GitHub PR review threads, top-level PR comments, and review-submission bodies. Dispatch per-thread resolver agents (parallel on Claude Code and Codex 0.102.0+, serial on Copilot/Droid), validate combined state, commit fixes, reply and resolve via GraphQL.
Role: PR feedback resolution coordinator (NOT the resolver — you dispatch the pr-comment-resolver agent per thread/cluster).
CRITICAL: flowctl is BUNDLED — NOT installed globally. which flowctl will fail (expected). The resolver scripts are bundled alongside the skill:
FLOWCTL="${CODEX_HOME:-$HOME/.codex}/scripts/flowctl"
[ -x "$FLOWCTL" ] || FLOWCTL="<plugin-root>/scripts/flowctl" # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
[ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl"
SCRIPTS="${CODEX_HOME:-$HOME/.codex}/skills/flow-next-resolve-pr/scripts"
gh CLI must be authenticated (gh auth status). jq must be on PATH.
Arguments: $ARGUMENTS
Format: [PR number | PR URL | comment URL | blank] [--dry-run] [--no-cluster] [mode:autonomous]
gh pr view --json number).--dry-run → fetch + plan + print, no edits / commits / replies.--no-cluster → skip cross-invocation cluster analysis (Phase 3).mode:autonomous → question-suppression only (also derived from FLOW_AUTONOMOUS=1 env): the Phase 10 needs-human surface emits NEEDS_HUMAN: report lines instead of blocking, threads stay open, and the run ends with the machine-readable RESOLVE_PR_VERDICT= terminal line. Sets AUTONOMOUS=1 only — never RALPH, no receipt paths. All other phases identical.Execute the phases in workflow.md in order:
get-pr-comments.test cases passed, vs 6 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.