
Receiving Code Review
This teaches Claude how to handle code review feedback without the performative "You're absolutely right!" responses that violate its guidelines. The core workflow is verify before implementing, ask before assuming, and push back with technical reasoning when reviewers are wrong. It distinguishes between trusted feedback from your partner (implement after understanding) and external reviewers (check against the actual codebase first, apply YAGNI, verify it won't break things). The enforcement is strict on banning gratitude theater and requiring clarification of all unclear items before touching any code. Honestly most useful for the specific anti-patterns it calls out, like implementing suggestions that break existing functionality or add unused features just because a reviewer suggested them.
- skills.sh installs
- 458
- GitHub stars
- 39.4K
- last updated
- Jun 3, 2026
Install
$ npx -y skills add sickn33/antigravity-awesome-skills --skill receiving-code-review --agent claude-codeInstalls into .claude/skills of the current project.
Files
Code Review Reception
Overview
Code review requires technical evaluation, not emotional performance.
Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.
The Response Pattern
WHEN receiving code review feedback:
1. READ: Complete feedback without reacting
2. UNDERSTAND: Restate requirement in own words (or ask)
3. VERIFY: Check against codebase reality
4. EVALUATE: Technically sound for THIS codebase?
5. RESPOND: Technical acknowledgment or reasoned pushback
6. IMPLEMENT: One item at a time, test each
Forbidden Responses
NEVER:
- "You're absolutely right!" (explicit CLAUDE.md violation)
- "Great point!" / "Excellent feedback!" (performative)
- "Let me implement that now" (before verification)
INSTEAD:
- Restate the technical requirement
- Ask clarifying questions
- Push back with technical reasoning if wrong
- Just start working (actions > words)
Handling Unclear Feedback
IF any item is unclear:
STOP - do not implement anything yet
ASK for clarification on unclear items
WHY: Items may be related. Partial understanding = wrong implementation.
Sponsors
Details
- Repository
- github.com/sickn33/antigravity-awesome-skills
- Categories
- Git & Pull Requests, Code Review & Quality
- First seen
- Jun 3, 2026
More from sickn33/antigravity-awesome-skills
All 708- Rust Pro458
- Golang Pro455
- Firecrawl Scraper454
- Finishing A Development Branch453
- Api Testing Observability Api Mock451
- Free Tool Strategy451
- Telegram Automation451
- Slack Gif Creator450
- Codebase Cleanup Tech Debt448
- Referral Program446
- Popup Cro445
- Frontend Mobile Security Xss Scan444
- Frontend Mobile Development Component Scaffold442
- Prompt Engineering Patterns442
- C Pro439
- Legal Advisor439
- Segment Cdp438
- Typescript Pro438
- Seo Content Writer437
- Tavily Web437
- Code Review Ai Ai Review436
- Database Optimizer436
- Ethical Hacking Methodology436
- Seo Keyword Strategist435