requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Security Assessment
About requesting-code-review
The 'requesting-code-review' skill facilitates the process of code reviews in software development, ensuring that work meets the necessary requirements before proceeding to subsequent stages. This skill addresses the common challenges developers face, such as overlooking critical issues or missing project requirements, by promoting a culture of early and frequent reviews. By integrating a structured approach to code assessment, it minimizes the risk of cascading problems that can arise from unchecked code changes, ultimately enhancing the quality and reliability of the software product.
FAQ
When should I request a code review?
You should request a code review after each task in subagent-driven development, after completing a major feature, and before merging to main.
What if I am stuck on a problem?
You can request a code review to gain a fresh perspective and potentially find a solution.
Are there any critical issues I should never ignore?
Yes, you should never skip a review because a task seems simple, ignore critical issues, or proceed with unfixed important issues.
Can I push back against feedback?
Yes, if you believe the reviewer is wrong, you should push back with technical reasoning and provide evidence.
Is there a specific format for dispatching the code-reviewer subagent?
Yes, you need to fill out a template at 'code-reviewer.md' with specific placeholders.
Install requesting-code-review
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
davila7/claude-code-templates