Skip to content
Back to skills

Receiving Code Review

ASecurity

Receive code review feedback constructively—verify claims, prioritize fixes, push back with evidence when needed. Use when acting on reviewer comments or preparing a second review round.

  • 25 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 6, 2026
ai-agentscode-reviewgitapisecurity

Works with

  • api

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add charlieviettq/awesome-agent-skill --skill receiving-code-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Receiving Code Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Receiving Code Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/charlieviettq-receiving-code-review-awesome-agent-skill/badge)](https://www.skillsdirectory.com/skills/charlieviettq-receiving-code-review-awesome-agent-skill)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: receiving-code-review
description: "Receive code review feedback constructively—verify claims, prioritize fixes, push back with evidence when needed. Use when acting on reviewer comments or preparing a second review round."
allowed-tools: Read, Glob, Grep
---

# Receiving code review

## Mindset

- Reviewers surface risk you may have missed; treat feedback as input, not orders.
- Verify technical claims before changing code (read code, run tests).

## Workflow

1. **Read fully** — understand intent, not only the literal suggestion.
2. **Clarify** — if feedback is vague, ask one focused question before partial implementation.
3. **Verify** — reproduce issue or confirm the concern in code; do not assume the reviewer is correct.
4. **Prioritize** — correctness and security before style.
5. **Respond** — agree + fix, or disagree with evidence (snippet, test, spec).
6. **Batch** related fixes; avoid drive-by changes outside review scope.
7. **Confirm** — run verification before marking threads resolved.

## When to push back

- Suggestion breaks API contract without migration plan.
- Fix is out of PR scope (offer follow-up issue).
- Reviewer assumption is wrong (show counter-evidence).

## When to accept quickly

- Naming/clarity that matches project conventions.
- Missing tests for changed behavior.
- Security or data-handling gaps.

## Anti-patterns

- Defensive replies without technical substance.
- Blindly applying every suggestion without understanding.
- Scope creep disguised as "while we're here".
- Implementing every comment without verifying technical accuracy.

## Related

`requesting-code-review`, `github-comment-triage`, `verify-before-done`

*Review handling patterns inspired by [obra/superpowers](https://github.com/obra/superpowers) (MIT).*

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…