← ClaudeAtlas

task-reviewlisted

Review a completed task branch with one independent parallel review panel and write a self-contained findings todo-list under reviews/. Retains every review pass until finish-task removes the task's review files. Never remediates; the user runs review-fix-worker for fixes. Use standalone after implement-next-task.
SrdjanCoric/skills · ★ 18 · AI & Automation · score 64
Install: claude install-skill SrdjanCoric/skills
# Task Review Review the diff between `HEAD` and a fixed base with independent Standards, Spec, conditionally applicable Bug, and conditional Security lenses. Run the panel once, with each active lens in its own subagent in parallel. Write every accepted finding to a todo-list file under `reviews/` in the repository. Do not fix findings here: remediation is the manual `review-fix-worker` loop, and a clean or fully resolved review unblocks `finish-task`. Invocation authorizes creating workflow files under `reviews/` and adding the `reviews/` ignore entry to `.gitignore` when missing. Never delete or overwrite a review file; `finish-task` removes all review files for the completed task. Never modify the implementation under review. Never write any other review document or create review scaffolding outside `reviews/`. ## Inputs Accept these optional inputs: - `base`: the fixed point for a three-dot diff, such as `main`, a branch, or a commit; - `spec`: the originating task, plan, or specification as a path or verbatim text; - `task`: the local task-file path when one exists; - `change-class`: `plan-only`, `documentation-only`, `dependencies`, `configuration`, `code`, or `mixed`; - `validation-tier`: `documentation`, `focused`, or `canonical`. When invoked standalone: 1. Ask for `base` if it is absent. 2. Resolve `spec` from a supplied path, issue reference in commits, or matching plan or spec file. 3. If `change-class` or `validation-tier` is absent, inspect the fixed bas