agentsclimarketplace
Sign in

Code review reception

Skill jagreehal/jagreehal-claude-skills/skills/code-review-reception

Receives code review feedback through technical verification rather than performative agreement or blind implementation. Use this skill when receiving review comments, before implementing reviewer suggestions, when feedback is unclear, or when a suggestion may be wrong for this codebase. Do not use when/for authoring reviews of others' code or when branch-completion is only about landing already-agreed work.From its SKILL.md

Install
npx -y skills add jagreehal/jagreehal-claude-skills --skill code-review-reception

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, as published. Nobody here has run it

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

  1. READ all feedback without reacting.
  2. UNDERSTAND: restate each requirement (or ask).
  3. VERIFY each suggestion against the codebase.
  4. EVALUATE: technically sound for THIS codebase?
  5. RESPOND: technical acknowledgment or reasoned pushback with evidence.
  6. 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.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.