Menu
Use to review material code or behavior changes before completion; review and same-boundary follow-up handoff only, no direct edits.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use to plan an AI/LLM evaluation strategy; advisory planning only, no implementation or QA closure.
Use to investigate a bug or incident and gather evidence before a fix; investigation only, implementation stays with the executor.
Use to review documentation for consistency and accuracy against code changes; read-only advisory, no doc rewrites or workflow closure.
Use for a delegated read-only advisory review through one explicit lens (security, performance, etc.); requires a named lens, makes no edits or closure.
Use to map an unfamiliar repository's architecture before brainstorming or planning; read-only discovery, no implementation edits.
Use to report the deterministic workflow checkpoint snapshot for a validated plan; snapshot only, no execution, QA, review, or compounder authority.
| name | imm-code-review |
| description | Use to review material code or behavior changes before completion; review and same-boundary follow-up handoff only, no direct edits. |
Load dist/imm-code-review.md, then review
the bounded change surface. Return actionable findings with evidence,
verification criteria, repairability, and Next Action.
Use the dist contract as source of truth, but preserve this loader-visible boundary:
activation planning uses the plugin-local wrapper resolved from the loaded skill location first: for an absolute skill path like /.../plugins/immune-brain/skills/imm-code-review/SKILL.md, use /.../plugins/immune-brain/bin/imm-activation-plan. If that is unavailable, try the repo-local plugins/immune-brain/bin/imm-activation-plan, then bun <plugin-root>/runtime/immune_brain_runtime.ts cli imm-activation-plan, then an installed imm-activation-plan wrapper when present. Do not report activation_runtime_unavailable just because the target repo lacks plugins/immune-brain; only use it when the loaded-skill plugin root, repo-local fallback, direct runtime fallback, and installed wrapper are all unavailable. Keep this separate from trigger_not_hit, explicit_required, and host_authorization_required.
Direct same-boundary findings emit a follow_up handoff to imm-work; the
follow_up is not a Plan mutation.
