kyoso-review git:20260715.78c5c36A

Immutable. This exact content is served forever at /api/v1/blob/b9d53ff164f2d36d.

---
name: kyoso-review
description: Use Kyoso when the user explicitly asks for multi-agent plan review, security review, CISA Secure by Design review, diff review, or a second opinion from Codex and Claude. Do not invoke implicitly unless the user clearly requests Kyoso or multi-agent review.
---

# Kyoso Review

Kyoso is a multi-agent review gate for AI coding workflows. It coordinates Codex and Claude through ACP and returns a structured plan, security, or diff review.

Use this skill when the user explicitly asks for:

- Kyoso
- multi-agent review
- plan review
- security review
- CISA Secure by Design review
- diff review
- second opinion from Codex and Claude

Do not use this skill for every coding task. It is intended for deliberate review checkpoints.

## Workflow

1. Determine whether the user wants a plan review, security review, or diff review.
2. Summarize the user's goal.
3. Gather relevant context:
   - repo summary
   - current plan if available
   - selected files
   - unified diff if available
   - constraints
4. Run the review through the first available path:
   - Prefer the corresponding Kyoso MCP tool when it is available:
     - `plan_review`
     - `security_review`
     - `diff_review`
   - If the MCP tools are unavailable, use the first available CLI path with JSON output:
     1. An installed `kyoso` executable on `PATH`.
     2. `npx -y @kyo-so/cli`.
     3. `bunx @kyo-so/cli`.
   - Append the review command to the selected CLI path:
     - `plan_review` -> `plan --goal <text> [--plan <path-or-text>] [--file <path>] --json`
     - `security_review` -> `security --goal <text> [--diff <path>] [--file <path>] --json`
     - `diff_review` -> `diff --base <ref> --head <ref> --json`
   - The CLI also accepts `--repo-summary`, repeatable `--constraint`, and repeatable `--file` flags. For a large review, adjust an agent timeout with `--set agents.<agent>.timeoutMs=<ms>`.
   - Run the CLI without a config trust flag first. Inspect `audit.warnings` in the JSON result; if it contains `untrusted config was not executed`, or the command fails with an untrusted-config message, ask the user whether to rerun with `--trust-config` to use it or `--ignore-config` to skip it. Never add `--trust-config` without confirmation.
   - Keep `--json` enabled and interpret the returned `decision` exactly like the MCP result.
5. Apply the [review-pass stop contract](#review-pass-stop-contract) before deciding whether to run another review.
6. Treat `decision: block` as a stop signal. Present the result to the user before implementing.
7. Treat `decision: approve_with_changes` as requiring changes to the plan or implementation.
8. Do not claim Kyoso modified files. Kyoso only reviews.

## Review-pass stop contract

- At one explicit review checkpoint, run one automatic review pass only.
- Record the returned `requestFingerprint`. Do not run the same fingerprint again in the same task.
- If `completion.status !== "complete"`, stop. Present the incomplete result; do not retry the same command or enter a finding-fix loop.
- A single confirmation pass is allowed only after fixing actionable, material findings from the first complete pass.
- After the confirmation pass, stop even when findings remain. Do not start a third pass without the user's explicit approval.
- Do not interpret `approve_with_changes` as permission to repeat until `approve`.