Menü
Run the patch workflow — implement a small, well-scoped change with no design phase. Use when the ticket already has a clear implementation path and design artifacts are not needed. Skips explore, design, and design-review.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
| name | patch |
| description | Run the patch workflow — implement a small, well-scoped change with no design phase. Use when the ticket already has a clear implementation path and design artifacts are not needed. Skips explore, design, and design-review. |
| user-invocable | true |
| args | [{"name":"feature-id","description":"Feature ID to patch (e.g., ORC-121). Auto-detected from worktree/branch if omitted.","required":false}] |
Route to the orchestrate skill with the patch schema.
orchestrate $ARGUMENTS --schema patch
Explore the codebase and write a discovery brief. Use when discovering scope, surveying a codebase, or starting a feature.
QA passed — merge branch to main, move ticket to Done, delete branch. Use after QA sign-off on a completed feature.
Run one fully-autonomous development iteration. Picks a ticket (from --focus or backlog via ideator), then runs the `orchestrator autopilot <slug>` workflow subcommand. This skill should be used when the user says 'autopilot', 'autonomous', 'self-improve'.
Create commits in logical groups. This skill should be used when the user says 'commit-group', 'group commits', 'organize commits', or when there are multiple unstaged changes that should be organized into atomic commits.
Complete feature — verify, signoff, archive. Runs only the complete phase of the orchestrate workflow. This skill should be used when the user says 'complete feature', 'finish feature', 'merge to main'.
Fetch curated, agent-optimized library documentation via Context Hub (chub). Use when implementing features that use external libraries, when Context7 returns noisy/incomplete docs, when you need language-specific or version-specific API docs, or when the user says "chub", "context hub", "get docs for X". Prefer this over Context7 for libraries in chub's registry — curated docs have less noise and better code examples.