review

Review a ztrack simple-sdlc issue and commit an approve or changes-requested verdict.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill review-volter-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/volter-ai/open-autonomy-compiler/tree/main/profiles/simple-sdlc/skills/review
Command: npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill review-volter-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides a deterministic review step for ztrack simple-sdlc issues, verifying that cited commits and evidence actually satisfy each acceptance criterion before an issue is marked done, without ever merging code itself. ## Core Features & Use Cases - Evidence-Based Review: Inspects the issue's cited commits and evidence in the developer's own worktree branch, accepting passing checks without redundant reruns. - Risk-Gated Verdicts: Applies risk-and-review standards, sending changes back when human-required paths are touched without approval or when claims do not hold. - Committed Verdicts: Records the outcome as a commit on the issue branch (review: done or review: changes-requested) so the verdict travels with the branch for the PM to integrate. - Use Case: A PM agent assigns an In Review issue that is green under ztrack check; this Skill validates the evidence, approves with ztrack issue edit --state done, and commits the verdict so the PM merges next tick. ## Quick Start Review the currently assigned ztrack issue by running ztrack check, verifying its cited evidence, and committing an approve or changes-requested verdict.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a ztrack simple-sdlc issue?▼

Read the ZTRACK_ISSUE environment variable, run ztrack check to confirm the issue is green, then inspect the cited commits and evidence for each acceptance criterion. Approve with ztrack issue edit --state done or send it back to in-progress, and commit the verdict.

How does the ztrack review verdict get integrated?▼

The reviewer commits the verdict on the issue branch with a message like "review: done $ZTRACK_ISSUE" so it travels with the branch. The PM agent merges the branch on the next tick; the reviewer never merges directly.

Can the review skill merge code into the main branch?▼

No. The reviewer is a verdict-only role that marks the issue done or sends it back to in-progress. Merging is exclusively the PM's responsibility after approval, enforcing a permission split between proposing and integrating code.

What happens if a review touches a human-required path?▼

If the change touches a human-required path or topic without explicit approval, the reviewer sends the issue back to in-progress, removes the ztrack:reviewing label, commits a changes-requested verdict, and reports OUTCOME: changes-requested human-required.

Why does ztrack review stop when ZTRACK_ISSUE is missing?▼

ZTRACK_ISSUE is an environment variable that scopes ztrack check and issue edit commands to the correct issue based on the branch. Without it the review cannot identify its assigned issue, so the procedure stops immediately.