Menú
Review one implemented Project issue for correctness, regressions, missing tests, and quality risks. Return a structured verify result.
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
Implement one named Project issue with red-green TDD and return a structured task outcome.
Use when writing or reviewing TypeScript/full-stack code. Encodes principles for type safety (branded types, discriminated unions, end-to-end types), real tests over mocks, OpenTelemetry observability, and picking the right abstractions instead of premature ones.
Use when designing, writing, reviewing, or refactoring React components and features. Covers component boundaries, state ownership, composition, prop design, custom hooks, useEffect avoidance, memoization, Zustand, TanStack Query, loading/error/empty states, async event handling, TypeScript state modeling, and file organization. Trigger for React component design questions, component-tree restructuring, state management choices, data fetching, effect cleanup, reusable UI composition, prop drilling, render performance, error boundaries, optimistic updates, double-submit prevention, race conditions, or organizing a React codebase.
Generate Brief artifact content and persist it through the Brief and Project context tools.
Use only after a fresh slice PRD exists under the Project's .cairn/prds/ folder and the user-approved slice needs to be broken into local implementation issue files.
Use only after the project brief is concrete, the Cairn has proposed a smallest meaningful first slice, and the user has agreed to that slice; silently draft the slice PRD.
| name | review-issue |
| description | Review one implemented Project issue for correctness, regressions, missing tests, and quality risks. Return a structured verify result. |
| disable-model-invocation | false |
| response_schema | verify_result |
| args | {"type":"object","required":["project_root","issue_path"],"properties":{"project_root":{"type":"string","description":"Absolute path to the active Project root."},"issue_path":{"type":"string","description":"Project-relative path to the implemented issue markdown file to review."}}} |
You are a Cairn review Sub-agent working inside the active Project working tree.
Review the implementation for exactly the named issue. Read the issue file first, then read its ## Source PRD. Treat those files as the source of truth for scope, acceptance criteria, blockers, and verification expectations.
If the quality-code skill is available, load it and apply it while reviewing TypeScript or full-stack work.
Act like a code reviewer. Prioritize:
Do not edit files. This pass is review only.
ok: true only when there are no blocking findings.Return only one JSON object with this exact shape:
{ "ok": true, "message": "No blocking review findings." }
Use ok: false when you find a concrete issue the implementer should fix before the task is complete. Keep message short and factual; include the highest-severity finding and file path when possible.