Menu
Use when receiving code review feedback before implementing suggestions, especially if unclear or questionable.
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
Systematic analysis and reasoning workflows. Use when performing audits, investigation, requirements analysis, risk analysis, scenario/edge-case enumeration, or design analysis that demands evidence-based, comprehensive coverage.
Code quality and safety standards. Activates when editing or reviewing code. Use for quality priorities, safety checks, and code correctness verification.
Use when performing coding tasks (implement features, fix bugs, refactor code). Orchestrates language detection, mode switching (normal/autopilot/full-auto), quality enforcement, and verification.
Break a problem into atomic, testable subproblems. Use when facing complex tasks, unclear requirements, or planning implementation strategy.
Start structured feature implementation workflow. Use when implementing new features, adding functionality, or building complete user-facing capabilities.
Use when starting work that needs isolated branches or parallel feature development using git worktrees.
| name | review-reception |
| description | Use when receiving code review feedback before implementing suggestions, especially if unclear or questionable. |
| allowed-tools | ["shell","read_file","apply_patch","update_plan"] |
| metadata | {"short-description":"Evaluate and apply review feedback rigorously"} |
Read these references:
~/.config/agent/core/behavior.md - Evidence-based reasoning~/.config/agent/domain/review/priorities.md - Review focus areasCode review requires technical evaluation, not performative agreement.
Core principle: Verify before implementing. Ask before assuming.
If any item is unclear, stop and ask for clarification before implementing anything.
Push back when:
Use technical reasoning and evidence.
Target: ${ARGUMENTS}