Menú
Compatibility wrapper that routes task resumption to first-class gza CLI resume/run-inline workflows
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
Review changes on current branch and output a structured review. Optionally post to PR with --pr flag, or apply non-blocking follow-ups inline with --apply-followups.
Run an interactive code-only review for a gza task's implementation branch and produce structured review output compatible with gza-task-improve
Check the implementation against the behavior specs in specs/behavior/. Reports where the code diverges from intended behavior — each divergence is either a code bug or a spec gap. The behavior spec is the source of truth; this skill never edits code or the spec.
Check the behavior spec set for coherence, ownership boundaries, and plain-language discipline without editing the spec or the code
Turn the recurring `watch` stuck-task pile into (1) a diagnosis of why each class is stuck, (2) the existing stuck rows actually cleared now, and (3) systemic prevention so it does not recur. Snapshots watch/incomplete/queue, buckets stuck tasks by failure class, dedups against already-tracked `system` work, unsticks each row by its clearing action (drop moot/dead/stale, spawn follow-up, hand review-loop rows to /gza-task-fix), then ranks and files `system`-tagged prevention fixes by blast radius (cascade-preventer first). Never merges, retries, resumes, deletes branches, or edits code.
Triage `gza incomplete` rows — classify each unresolved merge-unit lineage and recommend the right corrective action (drop moot leaves, escalate to fix, surface manual-resolve rebases, etc.). Never merges, retries, resumes, or deletes branches; never edits code.
| name | gza-task-resume |
| description | Compatibility wrapper that routes task resumption to first-class gza CLI resume/run-inline workflows |
| allowed-tools | Bash(uv run:*), AskUserQuestion |
| version | 2.0.0 |
| public | true |
Use first-class gza commands instead of manual inline reconstruction.
Require a full prefixed task ID (for example, gza-1234).
If no task ID is provided, list recent failed tasks and ask which one to resume:
uv run gza history --status failed --last 10
Preferred tracked resume flow:
uv run gza resume <TASK_ID> --run
If the user explicitly wants foreground inline execution through runner orchestration:
uv run gza run-inline <TASK_ID> --resume
Optional flags when requested:
uv run gza resume <TASK_ID> --run --no-docker
uv run gza resume <TASK_ID> --background
uv run gza run-inline <TASK_ID> --resume --no-docker
Report exit status and direct the user to gza log <TASK_ID> for full details.