requesting-code-review

Automate code review requests with a subagent and structured feedback.

Updated Aug 23, 2026

Search Tags:#git #testing #quality assurance #code review #development workflow #merge

Ready to run

npx skills add https://github.com/subham007ai/share-room --skill requesting-code-review-subham007ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/subham007ai/share-room/tree/main/.agent/skills/requesting-code-review
Command: npx skills add https://github.com/subham007ai/share-room --skill requesting-code-review-subham007ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps ensure code quality and adherence to requirements by facilitating a structured code review process before merging changes, preventing bugs and improving overall codebase health.

Core Features & Use Cases

Automated Review Dispatch: Integrates with a code-reviewer subagent to perform detailed code analysis.
Structured Feedback: Provides clear categorization of issues (Critical, Important, Minor) and actionable recommendations.
Use Case: After completing a new feature, you can use this skill to automatically trigger a code review, get feedback on potential issues, fix them, and then confidently merge your code.

Quick Start

Use the requesting-code-review skill to get feedback on your latest code changes.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate code review requests before a git merge?▼

To automate code review requests before a git merge, you can trigger a dedicated subagent to analyze your commit range. This process identifies code quality issues and enforces production readiness best practices using a structured markdown template.

What is the best way to structure feedback from a code review?▼

The best way to structure code review feedback is by categorizing issues into Critical, Important, and Minor levels. This approach provides clear, actionable recommendations to fix bugs and improve overall codebase health before merging changes.

How does a code reviewer subagent identify changes in my development workflow?▼

A code reviewer subagent identifies changes in your development workflow by using git commands to determine the specific commit range. It then analyzes these committed changes to provide structured feedback on potential issues.

Do I need git commands to trigger an automated code review?▼

Yes, you need git commands to trigger an automated code review because the process requires commit range identification. The skill uses these git commands to locate your latest changes before dispatching the review subagent.

When should I request a code review in the development workflow?▼

You should request a code review in the development workflow early and frequently, specifically after completing a new feature. Requesting reviews before merging prevents bugs and ensures adherence to project requirements.

Can I use this automated code review process without a templated markdown file?▼

No, you cannot use this automated code review process without a templated markdown file. The markdown template is required to provide structured review instructions and enforce best practices for code quality.