industrial/_project-template/skill-receiving-code-review
Claude Code and agent skill by industrial/_project-template
- community
Checking that the SKILL.md file is still in the repository.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Install
npx vskill@latest install industrial/_project-template/skill-receiving-code-reviewSKILL.md
The same SKILL.md was published earlier as industrial/_project-template/skill-receiving-code-review.
Code Review Reception
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
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
✅ Good: ```
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
✅ Good: ```
Source-Specific Handling
✅ Good: From External Reviewers
YAGNI Check for "Professional" Features
✅ Good: ```
Implementation Order
✅ Good: ```
When To Push Back
- Suggestion breaks existing functionality
- Reviewer lacks full context
- Violates YAGNI (unused feature)
- Technically incorrect for this stack
- Legacy/compatibility reasons exist
- Conflicts with your human partner's architectural decisions
- How to push back:
- Use technical reasoning, not defensiveness
- Ask specific questions
- Reference working tests/code
- Involve your human partner if architectural
- "Strange things are afoot at the Circle K"
Acknowledging Correct Feedback
✅ Good: When feedback IS correct:
Gracefully Correcting Your Pushback
✅ Good: If you pushed back and were wrong:
Common Mistakes
| Mistake | Fix | |
|---|---|---|
| Performative agreement | State requirement or just act | |
| Blind implementation | Verify against codebase first | |
| Batch without testing | One at a time, test each | |
| Assuming reviewer is right | Check if breaks things | |
| Avoiding pushback | Technical correctness > comfort | |
| Partial implementation | Clarify all items first | |
| Can't verify, proceed anyway | State limitation, ask for direction |
Real Examples
❌ Bad: Performative Agreement (Bad):
The Bottom Line
External feedback = suggestions to evaluate, not orders to follow.
Verify. Question. Then implement.
No performative agreement. Technical rigor always.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryChecking.openskills/skill-receiving-code-review/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/industrial/_project-template/skill-receiving-code-review)