agent-pipeline

Automates Issue-to-PR-to-Merge pipelines using GitHub Actions and AI agents with review loops.

4|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill agent-pipeline-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-pipeline
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/workflows/agent-pipeline
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill agent-pipeline-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually implementing well-specified GitHub issues is a bottleneck for development teams. This Skill sets up a fully automated pipeline where an AI agent implements labeled issues, opens pull requests, iterates on review feedback, and promotes merged changes — reducing human involvement to writing the issue and one review pass. ## Core Features & Use Cases - Four-Stage GitHub Actions Pipeline: Generates 1-implement.yml, 2-fix-review.yml, 3-merge-develop.yml, and 4-test-promote.yml workflows covering the full Issue → PR → Review → Merge lifecycle. - Agent-Agnostic Configuration: Switch between Claude and Codex agents with a single config line in .github/agent-pipeline.yml, with support for custom target branches, trigger labels, and review iteration caps. - Safety Guardrails: Enforces opt-in labeling, iteration caps, timeouts, PR-only changes, and human escape hatches with a full audit trail. - Use Case: A team with strong CI and a CLAUDE.md wants AI agents to handle routine feature issues. Run the setup operation to generate the config and workflow files, configure secrets, and verify the pipeline with a test issue. ## Quick Start Ask the agent to set up the agent-pipeline workflow in your repository by generating the config file and four GitHub Actions workflow files, then labeling a test issue to verify the pipeline fires.

Frequently Asked Questions about agent-pipeline

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

FAQPage Schema
How do I set up an automated Issue-to-PR pipeline with GitHub Actions?▼

Create a .github/agent-pipeline.yml config specifying the agent, trigger label, and target branches, then install four workflow files (implement, fix-review, merge, test-promote) into .github/workflows/. Label an issue with the trigger label to start the pipeline.

How do AI agents handle code review feedback automatically?▼

The 2-fix-review.yml workflow triggers when a PR review requests changes. The agent reads the review comments, applies fixes, and pushes updates, repeating up to the configured max_review_iterations before escalating to a human.

Can I use Codex instead of Claude for automated issue implementation?▼

Yes, the pipeline is agent-agnostic. Set agent: codex in agent-pipeline.yml and configure the OPENAI_API_KEY secret instead of ANTHROPIC_API_KEY. All other pipeline behavior remains identical.

What repositories should not use automated agent implementation pipelines?▼

Avoid repos without tests or CI, since the pipeline depends on test gates to validate agent output. Also avoid repos with vague issues lacking acceptance criteria, no CLAUDE.md conventions, or security-critical changes involving auth, crypto, or secrets.

Why does the GitHub Actions agent fail to push commits?▼

Push failures commonly occur when git authentication is lost after the claude-code-action runs, or when the agent tries modifying workflow files without permission. Re-set the remote URL with GITHUB_TOKEN before pushing and instruct the agent not to modify .github/workflows/.

How do I stop a runaway automated agent pipeline?▼

Remove the agent-pr label from the PR, add a needs-human-review label, close the PR, or cancel the run in the Actions tab. The pipeline also self-limits via iteration caps and per-run timeouts.