run

GitHub issue pipeline progression requires fetching issue state, rendering a canonical status table, and proposing a single next dispatch action based on lifecycle priority. This Skill manages the create, classify, plan, evaluate, execute, evaluate-pr, and merge sequence.

Human-in-the-loop gating for CI orchestration enforces strict confirmation before dispatching any classify, plan, evaluate, execute, or merge actions. The Skill defers classification and plan execution to a user-committed slate, ensuring you retain manual control over automated pipeline progression.

To enforce worktree workflow conventions and safe PR merge conditions, this Skill requires worktree-first branch routing and runs an autonomous merge gate for eligible PRs. It skips or flags PRs blocked by CI, mergeability, or merge-state checks.

Yes, you need gh, jq, git, and bash installed to manage GitHub issue stages. These dependencies are required for fetching issue states, querying JSON data, executing worktree workflows, and running the shell environment needed for pipeline orchestration.

Routing GitHub issues by path tiers evaluates execution readiness based on file changes, separating docs-only, multi-task, and quick-fix paths. The Skill applies dependency-aware readiness and label-driven stage routing to determine the correct next action.

You should delegate GitHub issue analysis to a dedicated hygiene skill when running `--analyze`, and delegate full-send autonomous end-to-end flows to a dedicated runner. This Skill coordinates interactive workflow management and requires strict confirmation gating for direct actions.