メニュー
Review changes in Codex with a risk-first workflow: establish scope, inspect high-impact files first, identify regressions/security issues, and report findings by severity.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Add new functionality by understanding existing patterns and dependencies before writing code. Locates where the feature belongs, studies conventions, implements following precedent, then verifies integration. Use when asked to add a feature, flag, endpoint, component, or module.
Thorough code review using token-efficient context gathering. Analyzes PRs, diffs, or staged changes by checking blast radius, complexity, and dependencies before reviewing the actual code. Use when asked to review a PR, review changes, or do a code review.
Systematically investigate and fix bugs using token-efficient context gathering. Reproduces the issue first, localizes with blame and history, traces the call path, then verifies the fix. Use when asked to fix a bug, investigate an error, or debug unexpected behavior.
Diagnose and fix performance issues by measuring before optimizing. Establishes baselines, identifies bottlenecks through call graphs and complexity analysis, then confirms improvements with numbers. Use when asked to optimize, speed up, reduce memory usage, or fix slowness.
Efficiently explore and understand an unfamiliar codebase using token-lean context gathering. Maps project structure, identifies key files, and builds understanding progressively without reading everything. Use when onboarding to a new project, asked to understand a codebase, or starting work in unfamiliar code.
Migrate frameworks, APIs, or language versions incrementally with verification at each step. Surveys the migration surface, batches work by dependency order, and commits after each verified batch. Use when asked to migrate between frameworks, upgrade major versions, or adapt to new API versions.
| name | code-review |
| description | Review changes in Codex with a risk-first workflow: establish scope, inspect high-impact files first, identify regressions/security issues, and report findings by severity. |
Review diffs with a risk-first approach.
Scope -> Risk map -> Deep review -> Verify assumptions -> Output
git status --short
git diff --stat
git diff
For branch/PR-style review:
git log --oneline --decorate -n 20
git diff <base>...HEAD --stat
git diff <base>...HEAD
Prioritize files that are:
bin/, exported modules, shared utilities)Useful probes:
rg -n "export |spawn|exec|rm -rf|chmod|process\.env|token|secret" src bin
rg -n "<changed symbol>" src test
For each high-risk file, check:
npm test
node bin/<changed-tool>.mjs --help
Run targeted commands that exercise changed behavior.
## Findings
- [severity] path:line - issue, impact, fix recommendation
## Open Questions
- Missing context needed for confidence
## Summary
- Overall risk and release recommendation
Severity: critical, warning, nit.