This one's about not being a pushover when someone drops review feedback on your code. It walks you through actually verifying suggestions against your codebase before implementing them, especially from external reviewers who might not know the full context. The pattern is straightforward: read, understand, verify it won't break things, then respond with technical reasoning or just fix it. What I like is the YAGNI check for when reviewers suggest "implementing properly" on features nobody even calls. It also bans performative responses like "Great point!" in favor of either asking clarifying questions or just showing the fix in code. Useful if you tend to auto-accept feedback without thinking it through first.
npx -y skills add ganyuanran/aegis --skill receiving-code-review --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
github/awesome-copilot
microsoft/win-dev-skills
github/awesome-copilot
github/awesome-copilot