← ClaudeAtlas

gza-task-reviewlisted

Run an interactive code review for a gza task's implementation branch, always running verify_command and producing structured review output compatible with gza-task-improve
mhawthorne/gza · ★ 11 · Code & Development · score 80
Install: claude install-skill mhawthorne/gza
# Gza Task Review Run an interactive code review for a specific gza task. Every review iteration must do both the normal code review work and an independent `verify_command` run from `gza.yaml`; verify is not a short-circuit. Produces structured review output that `/gza-task-improve` can consume. Use this when automated review iterations are exhausted, or when you want to review a task interactively. ## Inputs - Required: full prefixed task ID (for example, `gza-1234`) - Optional: `--pr` — also post the review as a PR comment If the user did not provide a task ID, ask for it before proceeding. Use the full prefixed task ID as provided. ## Process ### Step 0: Confirm review inputs without switching branches Manual `/gza-task-review` must stay compatible with repositories that forbid ad hoc git commands. Do not run `git checkout`, `git switch`, or other manual branch-switching commands as part of this skill. Before proceeding, make sure at least one of these is true: - The current workspace/worktree was already prepared on the implementation checkout by Gza or another documented non-forbidden workflow, so running `verify_command` here will evaluate the intended implementation. - The caller already provided authoritative diff context, so the review can use that diff even if this workspace is not on the implementation checkout. If neither is true, stop and ask the user to either: - rerun `/gza-task-review` from a prepared implementation checkout/worktree, or - provide t