name	pi-superworkers-code-review
description	Run Matt Pocock's two-axis code review through Pi Superagents for an unattended pi-superworkers issue worker.

Pi Superworkers Code Review

Use this adapter instead of directly following the upstream code-review skill's Agent/code-reviewer dispatch instruction. Preserve its two independent axes: standards and issue-spec compliance.

The worker provides a review packet directory containing these files:

brief.md — issue requirements, fixed point, and plan location;
implementation-report.md — implementation head and review context;
diff.patch — the exact fixed-point..HEAD diff.

Focused child-test policy: this overrides repository-level full-suite instructions. Marked child sessions may run only explicit issue-relevant test files or cases. Do not run the repository-wide/full-suite command from this session. The full suite runs only from /sw-close-parent.

Dispatch

Read the packet and the upstream code-review skill for its review criteria.
Make one parallel Pi Superagents dispatch with tasks: [ containing:
- sp-code-review for the Standards axis. Its task must include all three packet paths and ask for documented-standard violations, baseline smells, bugs, maintainability risks, and test-coverage concerns.
- sp-spec-review for the Spec axis. Its task must include all three packet paths and ask for missing, partial, incorrect, or unrequested issue requirements.
Do not use the generic Agent tool or invent a code-reviewer role.
Treat DONE_WITH_CONCERNS, NEEDS_CONTEXT, and BLOCKED as findings that prevent a clean review. Resolve substantive findings or escalate missing product/design decisions.
After fixes, commit them, regenerate the packet so diff.patch covers the same fixed point and current HEAD, then dispatch both reviewers again.
Select a focusedTestCommand that satisfies the focused child-test policy: it must be narrow, issue-relevant, and never the repository-wide/full-suite command reserved for /sw-close-parent.

Only report a clean result when both reviewers return DONE with no unresolved substantive findings. The parent worker owns the final JSON contract and runs the focused test command independently.

Pi Superworkers Code Review

Use this adapter instead of directly following the upstream code-review skill's Agent/code-reviewer dispatch instruction. Preserve its two independent axes: standards and issue-spec compliance.

The worker provides a review packet directory containing these files:

brief.md — issue requirements, fixed point, and plan location;

implementation-report.md — implementation head and review context;

diff.patch — the exact fixed-point..HEAD diff.

Dispatch

Read the packet and the upstream code-review skill for its review criteria.

Make one parallel Pi Superagents dispatch with tasks: [ containing:

sp-code-review for the Standards axis. Its task must include all three packet paths and ask for documented-standard violations, baseline smells, bugs, maintainability risks, and test-coverage concerns.
sp-spec-review for the Spec axis. Its task must include all three packet paths and ask for missing, partial, incorrect, or unrequested issue requirements.

Do not use the generic Agent tool or invent a code-reviewer role.

Treat DONE_WITH_CONCERNS, NEEDS_CONTEXT, and BLOCKED as findings that prevent a clean review. Resolve substantive findings or escalate missing product/design decisions.

After fixes, commit them, regenerate the packet so diff.patch covers the same fixed point and current HEAD, then dispatch both reviewers again.

Select a focusedTestCommand that satisfies the focused child-test policy: it must be narrow, issue-relevant, and never the repository-wide/full-suite command reserved for /sw-close-parent.

Only report a clean result when both reviewers return DONE with no unresolved substantive findings. The parent worker owns the final JSON contract and runs the focused test command independently.

pi-superworkers-code-review