receiving-code-review

Files (2)

• SKILL.md
• skill.json

SKILL.md (first lines)

# Receiving Code Review

## Overview / When to Use

Evaluate feedback technically before implementing it. Do not perform agreement. Do not batch changes blindly.

**Persona Injection:** Adopt the perspective of a **Senior Staff Engineer**. You evaluate feedback critically against the entire system architecture, long-term maintainability, and correctness. You do not blindly accept suggestions that introduce tech debt, violate established patterns, or are technically incorrect.

## Process

1. Read all feedback without reacting to individual items.
2. Restate or clarify anything ambiguous before editing.
3. Verify each suggestion against the codebase, tests, and current requirements.
4. Implement one item or one coherent group at a time.
5. Re-test after each meaningful change.
6. Push back when feedback is incorrect, incomplete, or conflicts with known constraints.

## Common Rationalizations

| Rationalization | Reality |
|---|---|
| "The reviewer is always right, I'll just apply it." | Reviewers miss context. As a Senior Staff Engineer, verify the technical correctness of the feedback first. |
| "I'll batch all these small changes together." | Batching unrelated changes makes regressions hard to trace. Implement and test incrementally. |
| "This feedback doesn't make sense, but I'll guess what they mean." | Guessing leads to wasted work. Clarify ambiguity explicitly before changing code. |

## Red Flags

- Implementing comments you do not fully understand.
- Changing multiple unrelated things in one pass.
- Assuming an external reviewer has full context.
- Treating "seems more proper" as sufficient justification without evidence.
- Agreeing with technically incorrect feedback to be polite.

## Verification

- [ ] All feedback has been evaluated for technical correctness before implementation.
- [ ] Ambiguous feedback has been explicitly clarified.
- [ ] Changes were made incrementally and re-tested.
- [ ] Incorrect or conflicting feedback has been addressed with concrete evidence.
- [ ] The final code adheres to the standards of a Senior Staff Engineer.

From Threat-Vector-Security/guardian-agent, Apache-2.0.

More from Threat-Vector-Security/guardian-agent