pipeline

Automate GitHub issues and pull requests through a 13-stage label-driven state machine.

3|1|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/accidental-hedge-fund/agent-pipeline --skill pipeline-accidental-hedge-fund
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/accidental-hedge-fund/agent-pipeline/tree/main/plugin/pipeline/skills/pipeline
Command: npx skills add https://github.com/accidental-hedge-fund/agent-pipeline --skill pipeline-accidental-hedge-fund

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual overhead of advancing GitHub issues through complex multi-stage development workflows, replacing ad-hoc coordination with a deterministic 13-stage state machine that handles planning, implementation, review, and gating automatically.

Core Features & Use Cases

  • 13-Stage State Machine: Automatically transitions issues from backlog through planning, implementing, review rounds, fix loops, pre-merge, eval-gate, and shipcheck-gate to pipeline:ready-to-deploy.
  • Cross-Harness Review: Uses Claude Code for implementation and Codex for review (or inverted), ensuring every change is cross-reviewed by a different harness.
  • GitHub-Native: Operates directly on GitHub issues and PRs using labels, comments, and worktrees—no external project management tools needed.

Quick Start

Use the pipeline skill to advance issue 419 through the dev pipeline by running the slash command or asking the AI to push the issue forward to ready-to-deploy.

Frequently Asked Questions about pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate advancing GitHub issues through a development pipeline to ready-to-deploy?

A label-driven 13-stage state machine automates advancing GitHub issues from backlog through planning, implementation, cross-harness review, fix loops, and gating stages to ready-to-deploy. It operates natively on GitHub issues and PRs using labels, comments, and worktrees.

What is cross-harness code review and how does it work for pull requests?

Cross-harness code review uses Claude Code for implementation and Codex for review, or inverted, ensuring every pull request change is cross-reviewed by a different harness. This automated mechanism eliminates manual coordination during the review and fix loop stages.

Do I need Node.js and GitHub CLI to automate issue tracking with a state machine?

Yes, automating issue tracking requires Node.js 24+, GitHub CLI authentication, and both Claude Code and Codex CLIs installed and authenticated on PATH. These dependencies are mandatory to run the scripts that execute the 13-stage label-driven transitions.

Can I use label-driven pipeline automation for complex software development workflows?

Yes, label-driven pipeline automation applies to software development workflows requiring cross-harness code review, automated planning, implementation, testing, and gating stages. It handles complex multi-stage transitions from backlog to ready-to-deploy deterministically.

What are the limitations of automating GitHub issue state transitions with this approach?

Limitations include the strict requirement for Node.js 24+, GitHub CLI, and both Claude Code and Codex CLIs installed on PATH. It is designed exclusively for GitHub-native workflows and does not support external project management tools or platforms outside the GitHub ecosystem.