This is a structured approach to triggering code review checkpoints in your Claude workflow, treating review as a formal step rather than an afterthought. The creator advocates mandatory reviews after subagent tasks, major features, and pre-merge, with optional reviews when you're stuck or before refactoring. It's essentially a discipline framework more than tooling. The value here is in codifying when to pause and review, which is useful if you're running multi-agent workflows where code can accumulate quickly without human checkpoints. Whether you need a skill file to remember to review your code is debatable, but if you're coordinating multiple Claude instances or subagents, having explicit review gates makes sense.
npx -y skills add bobmatnyc/claude-mpm-skills --skill "Requesting Code Review" --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
cursor/plugins
github/awesome-copilot
alirezarezvani/claude-skills
microsoft/win-dev-skills