Menu
Process GitHub issues — load issue, analyze type/complexity/areas, select workflow, execute agents, create PR with 'Fixes #X'
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Ultracode / Max-Parallel mode — dynamic workflows fan work out across tens–hundreds of adversarially-verified parallel subagents for large, decomposable jobs (codebase-wide audits, big migrations, cross-checked research). Opt-in; higher token spend.
Smart Routing — the DEFAULT CC_GodMode routing policy. Risk-based, minimal-agent paths that preserve required safety gates for the changed scope.
Release sprint workflow: version-at-release via tooling, CHANGELOG [Unreleased] flow, release invariant checks, tags, GitHub Releases, RCs. Authoritative law: docs/orchestrator/VERSIONING.md
Plan-first orchestration (ADR-004): comprehensive PLAN.md, sprint files with write-scope ownership, preflight checks, serialized integration, and the release sprint. Use for any non-trivial or multi-part request BEFORE dispatching agents.
Expanded department-based orchestration for large cross-domain CC_GodMode work. Freezes ownership, handoffs, and write scopes before implementation.
Bootstrap repo-local governance before CC_GodMode workflows run in an empty, newly initialized, or undocumented workspace. Use proactively when a project has no CLAUDE.md, no README, or no clear structure yet.
| name | issue-processing |
| description | Process GitHub issues — load issue, analyze type/complexity/areas, select workflow, execute agents, create PR with 'Fixes #X' |
"Process Issue #X"
1. @github-manager loads issue #X from GitHub
↓
2. Orchestrator analyzes issue:
↓
3. Select & execute appropriate workflow
↓
4. @github-manager creates PR with "Fixes #X"
When analyzing a loaded issue, determine:
| Dimension | Options | How to Determine |
|---|---|---|
| Type | Bug / Feature / Enhancement / Docs | Issue labels, title keywords, description |
| Complexity | Low / Medium / High | Scope of changes, number of files, dependencies |
| Areas | API / UI / Backend / Infrastructure / Docs | File paths mentioned, components affected |
| API Impact | Yes / No | Does it touch critical API paths? |
| Type | Complexity | Workflow |
|---|---|---|
| Bug | Any | Bug Fix workflow |
| Feature | Any | Feature workflow |
| Enhancement | Low | Bug Fix workflow |
| Enhancement | Medium/High | Feature workflow |
| Docs | Any | @scribe only |
| Any | Any + API Impact | API Change workflow |
The PR created by @github-manager MUST include:
| Label | Implication |
|---|---|
bug | Bug Fix workflow |
enhancement | Feature workflow |
api | API Change workflow (include @api-guardian) |
docs | Documentation only (@scribe) |
security | Force @validator security check |
performance | Add performance metrics to @tester |
urgent / hotfix | Emergency workflow (streamlined) |