jagreehal Code Review Reception
Critical rules
- Verify before implementing. A suggestion is a hypothesis, not a command.
- Technical correctness before social comfort. No performative agreement.
- If any item is unclear: STOP; ask before implementing anything.
- Implement one item at a time; test each; confirm no regressions.
- Acknowledge correct feedback through action, not praise.
- Before drafting replies or pushback, read references/examples.md.
Workflow
- READ all feedback without reacting.
- UNDERSTAND: restate each requirement (or ask).
- VERIFY each suggestion against the codebase.
- EVALUATE: technically sound for THIS codebase?
- RESPOND: technical acknowledgment or reasoned pushback with evidence.
- IMPLEMENT in order: blocking → simple → complex; test each fix.
Resources
- references/examples.md — unclear feedback, pushback, YAGNI, acknowledgment, rationalizations. Read when responding or unsure.
Validation
Before responding:
- All feedback read; requirements restated or clarified
- Each suggestion checked against the codebase
Before claiming done:
- One item at a time; each tested; no regressions
- Correct items acknowledged factually; wrong ones pushed back with evidence
Constraints
- Not for authoring reviews of others' code.
- Related:
verification-before-completion,tdd-workflow,debugging-methodology,critical-peer.