Menu
Code, PR, diff, branch, or commit review; git diff, git show, or change comparison. Not for debugging or design critique.
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
Pi extensions and tool policy: extensions/*.ts, hooks, registerTool, promptGuidelines, registerCommand, footer/status UI, tool_result, session hooks, or subprocesses. Not for slash-command placement; use pi-command.
README, CHANGELOG, docs/, RFCs, ADRs, guides, or Markdown structure. Not for prose cleanup or archival work.
Prose cleanup for filler, hype, vague claims, repetition, detection tells, or uncited specifics. Not for Markdown architecture or archival work.
Requirements, user stories, acceptance/verification criteria, or testable outcomes. Not for PRD drafting (/prd) or Pi /goal prompts.
Use for /prd-it or to draft, refine, or review a Product Requirements Document. Not for acceptance criteria, planning, or Pi /goal prompts.
Pi session, trace, metrics, routing, workflow-friction, workflow-telemetry, usage, or local JSONL analysis with DuckDB. Use for aggregating or correlating Pi runtime logs. Not for adding telemetry, generic SQL/database design, or non-Pi logs.
| name | code-review |
| description | Code, PR, diff, branch, or commit review; git diff, git show, or change comparison. Not for debugging or design critique. |
Use code-review only when reviewing a change set for findings. Use analysis-workflow for general troubleshooting and least-astonishment while making edits.
Report only issues that are demonstrably reachable and worth fixing. Suggestions are allowed, but label them separately from required findings.
.vscode/, .claude/, .gemini/, .cursor/, .github/workflows/,
.forgejo/workflows/, package lifecycle scripts, setup scripts, and go:generate directives
as security-sensitive executable or agent-instruction surface.[severity] Title
Evidence: <file:line and why the path is reachable>
Impact: <user/system consequence>
Required fix: <specific change or invariant>
| Severity | Meaning |
|---|---|
| Critical | data loss, credential exposure, remote exploit, total outage |
| High | common path broken, security boundary bypass, major regression |
| Medium | real bug with bounded impact |
| Low | minor correctness/maintainability issue |