fullsend

Orchestrate GitHub-issue-driven CI workflows with classification, planning, execution, and conditional merging.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/rjskene/pipeline --skill fullsend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fullsend
Source: https://github.com/rjskene/pipeline/tree/main/skills/fullsend
Command: npx skills add https://github.com/rjskene/pipeline --skill fullsend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the need to manually coordinate multi-step, human-checkpoint CI workflows driven by GitHub issues, so issues can move from classification and planning through execution, PR evaluation, and merging with minimal operator intervention.

Core Features & Use Cases

  • Autonomous end-to-end orchestration: Chains classify → plan → evaluate plans → execute → evaluate PRs → greenlight/merge across a slate of issues.
  • Wave-based dispatch & dependency awareness: Batches work in waves to respect blocked/depends-on annotations and to reduce file-contention when issues touch the same paths.
  • PR safety gate before merge: Only auto-merges when evaluation verdict, CI rollup success, mergeability, and merge state meet strict conditions; otherwise leaves a clear block reason for manual merge.

Quick Start

Use /pipeline:fullsend 101 102 103 to run the full pipeline autonomously for the specified issue numbers.

Frequently Asked Questions about fullsend

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

FAQPage Schema
How do I automate GitHub issue CI workflows end-to-end from issue classification to pull request merge?

Automated GitHub-issue CI orchestration chains classification, planning, execution, PR evaluation, and conditional merging into a single autonomous pipeline run. It dispatches sub-skills in waves to handle multiple issues with minimal operator intervention.

What is wave-based dispatch for CI orchestration and how does it handle issue dependencies?

Wave-based dispatch batches GitHub issues to respect blocked and depends-on annotations while reducing file-contention. It groups issues touching the same paths into sequential waves, ensuring dependency awareness across the orchestrated CI pipeline.

How do I run an autonomous batch pipeline across multiple GitHub issues using tmux execution queues?

Trigger an autonomous batch run by passing issue numbers to the pipeline command, such as /pipeline:fullsend 101 102 103. The orchestrator sets up worktrees, dispatches tmux-based execution queues, and produces a final per-issue report.

Can I enforce a PR safety gate before auto-merging in an automated CI pipeline?

Yes, a strict PR safety gate only auto-merges when the evaluation verdict, CI rollup success, mergeability, and merge state all meet specific conditions. If checks fail, the pipeline leaves a clear block reason for manual merge.

Does autonomous GitHub issue orchestration work without external pipeline dependencies?

Autonomous GitHub issue orchestration runs without external dependencies by loading pipeline.config variables and dispatching internal sub-skills. It applies plan evaluation and worktree setup natively to manage the end-to-end CI workflow.

What are the limitations of auto-merge gating for CI-driven pull request evaluation?

Auto-merge gating requires strict conditions including evaluator outcomes and GitHub PR state checks. When CI rollup fails or mergeability is unconfirmed, the pipeline blocks the merge and flags the issue for manual review in the final report.