Menú
Interactive /gobby review launcher. Dispatches holistic-reviewer for an epic.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Instructions for using gcode CLI for code search and retrieval. Loaded on demand when project has a code index.
Pre-transition checklist for closing or reviewing tasks. Covers fresh verification evidence, commits, and memory gates.
Use when processing CodeRabbit review comments, CodeRabbit CLI reports, or `$gobby coderabbit [findings]` requests.
Use when creating, editing, or validating Gobby skills, especially when a skill must change agent behavior or become discoverable through gobby-skills.
Use when coordinating a full gobby build run for an epic or task, especially when the user assigns the current session as coordinator, asks for a coordination epic, wants build agents/worktrees monitored, or wants gobby build bugs fixed so future runs work unattended.
Router contract for provider-aware Gobby help and installed skill dispatch.
| name | review |
| description | Interactive /gobby review launcher. Dispatches holistic-reviewer for an epic. |
| version | 1.0.0 |
| category | core |
| triggers | review, gobby review, holistic review, epic review |
| metadata | {"gobby":{"audience":"interactive","depth":0}} |
Use this skill when the user invokes /gobby review to run the same holistic
epic reviewer that lifecycle dispatch uses, independent of gobby build.
The workflow definition is src/gobby/install/shared/workflows/review.yaml.
Resolve an epic task ref before dispatch. Accept #N, a numeric ref, or a
dotted task path. If the user does not provide one, ask for the task ref.
Ask for the I/D mode unless it is already clear from the user's request:
I) Interactive - dispatch holistic-reviewer and surface the run ids.
D) Delegated - dispatch holistic-reviewer and end the turn.
Persist the choice as value="interactive" | "delegated" for the handoff.
Both modes use the holistic-reviewer agent and the shared workflow YAML.
The holistic review loop checks the approved plan, aggregate implementation diff, validation evidence, and child task outcomes. The reviewer emits exactly one verdict:
approve_review(stage_name="holistic_qa")reject_review(stage_name="holistic_qa")escalate_taskUse the explicit user-facing summary approve / reject / escalate when
describing possible outcomes.
Run the review workflow with the resolved epic task id:
call_tool("gobby-workflows", "run_pipeline", {
"name": "review",
"inputs": {
"task_id": "<epic_task_ref>",
"mode": "<interactive|delegated>"
}
})
Surface the returned execution id. The spawned holistic-reviewer owns the
review verdict and terminates through its agent workflow.
close_task; lifecycle dispatch owns closure.holistic-reviewer or holistic-review methodology here.