epic-orchestrator

Orchestrates GitHub epics by steering a coding bot through issues, PRs, and merges.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/alkampfergit/cisharpai --skill epic-orchestrator-alkampfergit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-orchestrator
Source: https://github.com/alkampfergit/cisharpai/tree/main/.claude/skills/epic-orchestrator
Command: npx skills add https://github.com/alkampfergit/cisharpai --skill epic-orchestrator-alkampfergit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating a multi-issue GitHub epic implemented by an automated coding bot requires constant human oversight: triggering work, answering design questions, reviewing PRs, verifying CI and SonarCloud results, and merging safely. This Skill turns that into a disciplined, repeatable tick-based workflow where the operator never writes code but keeps the epic moving to completion. ## Core Features & Use Cases - Tick-based orchestration loop: Each run verifies identity, fetches fresh epic state via gh, evaluates every child issue against a state machine (not started, awaiting design answer, PR open), and takes exactly one appropriate action. - Strict C1-C6 PR gate: A sequential checklist covering CI status, SonarCloud zero-new-issues verification (beyond the misleading quality-gate banner), Copilot review requests via the only working method (gh pr edit --add-reviewer @copilot), finding verification against actual source, merge, and sibling-PR rebase notification. - Failure discrimination: Distinguishes real code failures from external outages (e.g., SonarCloud 5xx) before asking the bot to fix anything, and escalates genuinely ambiguous or risky decisions to the user. - Use Case: A team lead has an epic with 8 sub-issues being implemented by a bot account. They invoke this Skill periodically to check status, answer the bot's design questions, request and verify Copilot reviews, and merge clean PRs until the epic closes. ## Quick Start Ask the assistant to orchestrate epic #N in this repository, providing the orchestrator GitHub account, the bot account name, the trigger label, and the WIP limit.

Frequently Asked Questions about epic-orchestrator

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

FAQPage Schema
How do I orchestrate a GitHub epic with an automated coding bot?▼

Run one orchestration tick at a time: verify your gh identity, fetch the epic's sub-issues via the GitHub API, evaluate each issue's state, and take the single appropriate action such as adding the trigger label, answering a design question, or merging a clean PR.

How do I request a Copilot review on a GitHub pull request?▼

Run gh pr edit <PR> --add-reviewer @copilot with gh CLI 2.88.0 or later. Passing the bot's comment-author login or display name fails with a GraphQL error because Copilot's reviewable identity is typed as a Bot, and only the literal @copilot handle routes correctly.

Why does SonarCloud show a passing quality gate but still have new issues?▼

The quality gate only checks its configured conditions like ratings and coverage thresholds, not whether zero new code smells exist. Query the issues/search, measures, and qualitygates APIs separately to confirm new_violations is zero and every gate condition is OK.

How do I tell if a CI failure is a real code problem or an outage?▼

Fetch the actual failure log with gh run view --log, then curl the external service's status endpoint directly, such as SonarCloud's server version API. If the service returns 5xx, it is an outage; wait for recovery and rerun the failed job with gh run rerun --failed.

When should the orchestrator escalate to the user instead of deciding?▼

Escalate when the bot contradicts a binding design decision twice, a PR changes public API beyond its issue's scope, a fix games a quality metric, anything touches secrets or branch protection, or the same check fails three ticks running without an external outage.