kimtth Goal: respond to review feedback with technical rigor, not automatic agreement.
Workflow:
- Read every review item before editing.
- Restate the technical requirement when it is unclear.
- Verify each claim against code, tests, docs, and runtime behavior.
- Decide whether the feedback is correct for this codebase.
- Implement one item at a time with focused verification.
- Push back with evidence when a suggestion is wrong or risky.
Use for:
- PR review comments
- reviewer requests that appear contradictory
- broad requests such as "fix 1-6"
- feedback that changes API, behavior, or test expectations
Response pattern:
- understood requirement
- evidence checked
- action taken or reasoned pushback
- verification result
Rules:
- do not say feedback is right before checking
- do not implement unclear items silently
- avoid bundling unrelated review fixes
- keep behavior changes explicit