flow-next-resolve-pr

Featured

Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.

AI & Automation 695 stars 55 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
95
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# PR Feedback Resolver **Read [workflow.md](workflow.md) for full phase-by-phase execution. Read [cluster-analysis.md](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: ```bash 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. ## Input Arguments: $ARGUMENTS Format: `[PR number | PR URL | comment URL | blank] [--dry-run] [--no-cluster] [mode:autonomous]` - **Blank** → detect PR from current branch (`gh pr view --json number`). - **PR number / PR URL** → full mod...

Details

Author
gmickel
Repository
gmickel/flow-next
Created
8 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category