Skip to content
Agentmart
Submit a tool

receiving-code-review

Answering review comments: check each against the code, push back with reasons, record the outcome.

Skill by ayeo-io

IndexedApache-2.0★ 1
Write a review

Chalk Labs

Need help deploying receiving-code-review?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/ayeo-io-receiving-code-review

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Answering review comments: check each against the code, push back with reasons, record the outcome.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Nov 1, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/receiving-code-review

What's inside

Skill name
receiving-code-review
Description
Answering review comments: check each against the code, push back with reasons, record the outcome.
License
Apache-2.0
Instructions
43 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Receiving Code Review

There are two ways to answer a reviewer badly; agreeing too readily is the
more common.

**Check each suggestion against the code before you implement it.** Every
comment is a hypothesis about code the reviewer read faster than you wrote it.
A suggestion right about the symptom and wrong about the cause is the normal
case - implementing it verbatim leaves the symptom and adds a change nobody
needed.

**"You're absolutely right", before checking, is the failure this prevents.**
It converts the reviewer's guess into your commit, removing the second opinion
review existed to give.

**Push back with technical reasoning when the reviewer is wrong.** Show the case
their suggestion breaks, the constraint it misses, or the measurement that
contradicts it - not preference or seniority. If you
cannot produce a technical reason, they are probably right.

**Treat "implement this properly" as a question about scope.** Ask what breaks
today without it. If the answer is nothing, it is a separate issue, not a
review thread.

**Read the label first** (`${CLAUDE_PLUGIN_ROOT}/governance/strategies.md` `S12`; an unmigrated 5.x
project uses its own copy). Issue, suggestion, nitpick, question or
praise tells you what blocks the merge before you read the argument. If it is
missing, ask rather than guess.

**Say what you did.** Per comment: changed it, or did not and why. A resolved
thread with no reply is a decision nobody can audit, and a change with no
recorded reason is an assertion. Keep it short: *"Checked -
`validate()` runs before the cache write, so that race cannot happen here. It
can on the batch path; fixed there."*

## Anti-patterns

- **Reflexive agreement** - implementing without checking.
- **Reflexive defense** - explaining why the code is fine before reading properly.
- **Silent compliance** - changing it with no reply, so the reasoning is lost.
- **Deferring on authority** - the code does not know who filed the comment.

From ayeo-io/compass, Apache-2.0.

More from ayeo-io/compass

Signals

Stars
1
Forks
0
Open issues
23
Last commit (this folder)
Oct 20, 2026 (12 days ago)
Last release
Oct 20, 2026 (12 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from ayeo-io

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get receiving-code-review running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying receiving-code-review?

CallGet help
Cite this page

receiving-code-review skill. Agent Mart. https://agentmart.dev/skills/ayeo-io-receiving-code-review (last updated 2026-10-24)