--- description: "AILI local-review command generated from the backend-neutral canonical body." agent: rose subtask: false --- # /local-review User input: `$ARGUMENTS` Invoke the canonical report-first local-review utility. If a dedicated local-review capability is available, it may supply bounded review mechanics; this canonical Command remains the authority for target, gate, and result boundaries. Purpose: - Review a selected local target as a standalone non-delivery audit, classify findings first, and report skipped or `Unverified` lanes without mutating remote state. - A `/local-review` result is not lifecycle acceptance or SHIP, release, merge, archive, or closeout evidence. Target modes: - No args: review staged, unstaged, and untracked local changes. - `--base `: review the current branch/worktree against the merge base with the named base branch. - `--commit `: review the selected commit. - `--pr `: inspect PR metadata and diff only through the exact read-only GitHub CLI allowlist `gh pr view`, `gh pr diff`, and `gh pr list --head` when available; no other `gh` command is allowed in PR mode. - `--change `: review an OpenSpec change contract and evidence artifacts. - `--focus ` or adversarial wording: constrain emphasis, such as security, tests, data loss, performance, or adversarial review. - `--repair`: enter repair only after a categorized report exists and repair is explicitly authorized. Required behavior: - Resolve and report target scope, base/ref/commit/PR/change metadata, included untracked files, unavailable metadata, and skipped lanes before accepting findings. - For `--change `, read the conventional OpenSpec artifact paths directly instead of relying only on broad globs because local OpenSpec artifacts may be git-ignored or absent from snapshot-style search indexes. - Inspect full changed files and relevant tests, configuration, documentation, and callers when needed for high-confidence correctness, security, data-loss, compatibility, or test findings; otherwise mark the limitation `Unverified`. - Review across five axes — correctness, readability, architecture, security, and performance — after reading applicable artifacts and tests first when present. - Require Critical/Important findings to include evidence anchors, concrete failure mode, why existing guards do not catch it, and concrete fixes; zero findings is valid only with inspected scope, skipped checks, and evidence limits recorded. - Use fail-closed orchestration for selected lanes: missing/status-less lane output, unavailable required context, or unverifiable high-risk findings cannot become a clean `PASS`. - Produce a categorized report before repair. For an OpenSpec target, default to `openspec/changes//review-report.md`; for a non-OpenSpec target, ask once for a repository-local report path or obtain an explicit chat-only waiver with persistence marked `Unverified`. - Classify each finding by severity, category, source lane, evidence anchor, affected file or artifact, required action, repair owner, status, and re-review requirement. - Use verdicts: `BLOCKED`, `NEEDS_FIXES`, `NEEDS_REVIEW`, `PASS_WITH_UNVERIFIED`, `PASS`, `REPAIRING`, and `REREVIEW_REQUIRED`. - Report skipped checks, unavailable tools, stale evidence, and remaining `Unverified` items explicitly. - For large or harness-sensitive OpenSpec targets, `NEEDS_FIXES` and `BLOCKED` block BUILD continuation; `PASS_WITH_UNVERIFIED` permits continuation only after the user accepts each named `Unverified` item. Hard stops: - Do not override, replace, or depend on OpenCode's built-in `/review` command. - Do not replace `/ship` or claim release-readiness, merge-readiness, handoff-readiness, archive-readiness, or closeout readiness. - Do not use this audit as lifecycle acceptance or as SHIP/release/merge/archive evidence. - Do not push, create PRs, comment on GitHub, approve/request changes, merge, tag, publish, delete, reset, clean, or otherwise mutate remote state. - Do not run `gh api`, `gh pr checkout`, `gh pr comment`, `gh pr review`, `gh pr merge`, `gh pr create`, `gh repo clone`, or an equivalent remote-mutating command in PR mode. - Do not perform repair until after the categorized report exists and the user or current active contract explicitly authorizes repair. - Do not store or print secrets, tokens, private keys, cookies, raw logs, full transcripts, full file dumps, or private data in reports; use redacted path:line/type evidence instead. - Stop as `BLOCKED` when the target, base, report path, required permission, or evidence source is ambiguous and cannot be safely inferred. Output contract: - Resolved target, scope, base/ref/commit/PR/change metadata, and report path or chat-only waiver. - Files and artifacts inspected in full and files and artifacts sampled or skipped. - Checks and review lanes run, skipped, or marked `Unverified`, with reasons. - Categorized findings with severity, evidence anchors, required actions, repairability, owner, status, and re-review requirement. - Verdict from the local-review vocabulary and exact residual risks or `Unverified` items. - If repair is authorized: repair packages, affected verification to rerun, and re-review status.