receiving-code-review
Receiving Code Review
Apply technical rigor to review feedback — not performative agreement.
Step 1: Classify and prioritize each comment
Process comments in priority order — fix critical issues before addressing style.
| Priority | Category | Action |
|---|---|---|
| P0 | Security issue | Verify and fix immediately. These block merging. |
| P1 | Correctness bug | Verify independently. If confirmed, fix. If not, explain with evidence. |
| P2 | Performance concern | Verify with measurement, profiling, or big-O reasoning. Do not optimize without evidence of a real problem. |
| P3 | API/contract issue | Check if it would break consumers. Fix if yes, discuss trade-offs if debatable. |
| P4 | Style preference | Implement if it matches project conventions. Skip if purely personal preference with no convention behind it. |
| P5 | Nit / typo | Fix. These are cheap and reduce review noise. |
Step 2: Verify before implementing
More from beltonk/claude-code-agent-skills
coding-practices
Coding-specific practices for AI agents — scope discipline, read-before-write, simplest approach first, incremental development, verification, comment standards, security awareness, tool preferences, and shell discipline. Use when the agent is writing, editing, or reviewing code. Works alongside agentic-standards (which covers general behavior for all interactions).
4managing-memories
Covers the full memory lifecycle — when to save, what format to use, how to organize and deduplicate, how to recall relevant memories, and what to never persist. Use at natural breakpoints to capture user preferences, corrections, and project conventions, and at session start to load relevant context.
4scaffolding-projects
Provides a structured approach to starting new features or projects. Guides the agent through understanding requirements, exploring existing code, planning, incremental implementation, and verification. Use when asked to build something new — a feature, module, service, or project — to avoid jumping into code without context.
4handing-off-sessions
Captures structured session state for resuming work in a new session or handing off to another agent. Use at the end of a session, before context limits, or when the user asks to save progress. Not needed for trivial sessions (quick questions, one-line answers).
4compacting-context
Provides a structured 9-section summarization template for compressing long conversations while preserving critical details. Use when a session approaches context limits and history must be compressed without losing user intent, file changes, errors, or next steps.
4agentic-standards
Foundational behavioral standards for any AI agent — safety/reversibility framework, output quality, memory conventions, and prompt injection defense. Applies to all agent interactions including chat, analysis, writing, debugging, and coding. Use when setting up an agent, onboarding to a new project, or when behavioral baseline guidance is needed. For coding-specific rules, also load coding-practices.
4