When someone reviews your code, do not just nod and say yes. Stop and think. First read the feedback without reacting. Then ask yourself what they really mean. Check if their suggestion works for your specific codebase. Verify before you change anything. Do not use empty phrases like "Great point" or "You are right." Instead restate the requirement or ask a clear question. If the feedback is unclear, pause and ask for more details. It is better to wait than to fix the wrong thing. Technical correctness matters more than being polite. If a suggestion breaks your code or adds something you do not need, push back with facts. Your goal is to make the code better, not to please everyone.
Global
mkdir -p ~/.claude/skills/receiving-code-reviewProject
mkdir -p .claude/skills/receiving-code-reviewSource Repository
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge