with one click
with one click
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | corgispec-review |
| description | Review a completed Task Group via GitLab issue feedback. |
| license | MIT |
| compatibility | Requires openspec CLI. |
| metadata | {"author":"openspec","version":"2.0","generatedBy":"1.3.0"} |
Review a completed Task Group with quality checks and interactive approval.
openspec/changes/<name>/.gitlab.yaml exists with parent and group issue IIDsisolation.mode is worktree: worktree exists for this change (error if not)Read openspec/config.yaml for isolation settings.
If isolation.mode: worktree: Changes live inside worktrees, not the main checkout. Read references/worktree-discovery.md for the full discovery procedure. Quick summary:
openspec list --json, if it returns changes, use them<isolation.root>/ directories, verify each with git worktree list and check openspec/changes/<name>/ exists insideIf no isolation: openspec list --json directly. Auto-select if one, prompt if multiple.
If name provided by user, use it directly.
Read .gitlab.yaml for the group list. Check each group's labels via GitLab. Default to the first group in workflow::review state.
Read tasks.md. If the selected group's tasks are not all [x], stop.
Read child issue notes. If reviewer feedback exists, present it to the user before proceeding.
Run automated quality checks and assemble a Review Report.
Quality checks inform the decision. They do not decide the outcome.
Read references/quality-checks.md for the full quality check procedure (code quality, spec verification, functional testing, report format).
Post the review report to the GitLab child issue:
glab issue note <child_iid> --message "$REVIEW_REPORT"
Posting the report records evidence for the human gate. Do not change labels, close issues, update parent progress, or generate repair tasks in this step.
This step is MANDATORY. You MUST stop here and wait for user input.
Use the structured question/choice tool (e.g., question()) to present exactly these options.
Do NOT present them as plain text — use the interactive selection tool so the user can click/select directly:
Quality checks inform the decision. Only the user approves or rejects.
Do NOT proceed until the user explicitly chooses.
Read references/review-decisions.md for the full approve, reject, and discuss procedures.
references/repair-flow.md)All label changes, parent updates, and repair task generation happen only inside the approve or reject paths after the user chooses.
workflow::done (issue left open — closing removes it from board)tasks.md, child issue moved to workflow::in-progressIf you reached postconditions without asking the user in Step 5, you violated the contract. Stop and re-do Step 5.