skills.rest
FredoAi
FredoAiOFFICIAL
Explore all skills by this author →
GitHub

pipeline-state

Drives a GitHub issue pipeline state machine via a single rust-script CLI.

Updated May 18, 2026
Search Tags:#workflow automation#multi-agent#github issues#state machine#rust-script#audit log#ci pipeline
One-click install
npx skills add https://github.com/FredoAi/fredo --skill pipeline-state-fredoai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pipeline-state
Source: https://github.com/FredoAi/fredo/tree/main/.opencode/skills/pipeline-state
Command: npx skills add https://github.com/FredoAi/fredo --skill pipeline-state-fredoai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-agent work on GitHub issues requires a single authoritative writer for phase transitions, comments, labels, and metrics; this Skill loads the instructions for invoking the pipeline-state.rs state machine so agents never improvise phases or bypass guards. ## Core Features & Use Cases - Context loading at wake: Run the script with an issue number and agent name to receive the current phase, goals, playbook, validation status, and handoff before doing any work. - Single-writer GitHub actions: Create issues, post Status comments and timeline drafts, transition phases with enforced exit gates, manage worktrees, upload test evidence, and record audit verdicts — all through one deterministic script. - Metrics, audit, and integrity: Query per-issue or aggregate lifecycle metrics, generate audit evidence bundles and health reports, and run an anti-tamper verification over the append-only event log. - Use Case: A dispatched developer agent runs the loader, learns the feature is in the implementation phase, creates a detached worktree on the spec branch, and later the self-improver transitions testing to audit after a passing Tests Runs verdict. ## Quick Start Ask the agent to run rust-script on .opencode/scripts/pipeline-state.rs with your issue number and agent name to load the current pipeline context before starting work.

Frequently Asked Questions about pipeline-state

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

FAQPage Schema
How do I run the pipeline state machine for an issue?▼

Run rust-script .opencode/scripts/pipeline-state.rs with --issue <N> and --agent <your-name>. It returns a context block with the current phase, goals, playbook, validation status, and handoff, which you must read before doing any work.

How do I transition a GitHub issue to the next pipeline phase?▼

Use the transition action with the self-improver agent: --action transition --to-phase <phase>. Exit gates are enforced, such as a converged plan for planning or a passing Tests Runs verdict for testing, and done is only reachable through cleanup after a successful audit.

Can agents call gh issue create or git push directly?▼

No. The state machine is the single writer for all GitHub operations. The only exceptions are the developer pushing HEAD:spec/<N> and the self-improver's fast-forward doc-sync push to main; all other writes go through pipeline-state.rs actions.

What does BLOCKED mean in the script output?▼

BLOCKED means a guard or exit gate failed, such as a missing plan section or a failed verification guardrail. Do not retry or work around it; report the blocker reason to the orchestrator instead.

How do I verify the pipeline event log has not been tampered with?▼

Run the verify action, which scans the event and error logs for unparseable lines, out-of-order timestamps, and duplicate event IDs. INTEGRITY: OK confirms the append-only record is intact; any flag exits with code 3.

What are the prerequisites for uploading test evidence screenshots?▼

The gh CLI must be authenticated with push access and the gh-image extension installed via gh extension install drogers0/gh-image. Save screenshots under .opencode/tmp/<issue>/e2e/ first, then run the upload-evidence action to get a user-attachments URL.

Related Skills

Explore More Software Engineering Skills→
LamseyahEliasLamseyahElias

github-auth

Authenticate with GitHub using HTTPS tokens, SSH keys, or gh CLI.

Community
Intermediate
summarybotngsummarybotng
2

qcsd-production-swarm

Orchestrate a multi-agent swarm to assess post-release production health and generate recommendations.

Official
Advanced
MrSuttonmannMrSuttonmann
55

screenshots

Regenerate README UI screenshots for desktop and mobile views.

Community
Advanced
devantler-techdevantler-tech
2

ways-of-working

Codify engineering workflow guidance for planning, testing, reviewing, and shipping work.

Official
Advanced