Menu
Implement tasks from a Corgi change, one Task Group at a time
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Archive a completed change, close tracking issues, and sync delta specs
Think through ideas, investigate problems, or clarify requirements
Install, update, or verify Corgi GitFlow assets in a target project
Validate memory health across 14 checks — freshness, size caps, broken links, extraction completeness
Run the Corgi Loop — execute Task Group bundles (apply → verify → review-evidence) with automated lifecycle decisions
Propose a new change — create it and generate all artifacts in one step
| name | source-command-corgi-apply |
| description | Implement tasks from a Corgi change, one Task Group at a time |
Use this skill when the user asks to run the migrated source command corgi-apply.
Implement tasks from a Corgi change, one Task Group at a time.
Input: Optionally specify a change name (e.g., /corgi:apply add-auth). If omitted, infer from context.
Steps
Determine platform
Read openspec/config.yaml and check the schema field.
Check isolation mode (CRITICAL — do NOT skip)
Read openspec/config.yaml and check isolation.mode.
isolation.mode is worktree: the worktree MUST already exist (created by propose). The skill MUST resolve it and work inside it. If the worktree is missing, stop and report failure — do not create it during apply.isolation section is missing or mode is none: normal operation, no worktree needed.Dispatch to platform skill
schema: gitlab-tracked → Follow the instructions in the corgispec-apply-change skillschema: github-tracked → Follow the instructions in the corgispec-gh-apply skillThe selected skill owns the internal apply phases, including discover, develop, closeout, and review handoff. This wrapper only reads config, enforces isolation, dispatches by schema, and verifies postconditions.
Pass through all input
Forward the user's input (change name, etc.) to the selected skill as-is.
Verify postconditions
After the skill completes, verify:
[x] in tasks.mdisolation.mode is worktree: all local output changes are in the worktree, not main checkout