skills.rest
rahulsc
rahulscCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Dispatches specialized subagents to review code based on risk tiers.

Updated Aug 23, 2026
Search Tags:#git#testing#devops#quality assurance#code review#deployment
One-click install
npx skills add https://github.com/rahulsc/forge --skill requesting-code-review-rahulsc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/rahulsc/forge/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/rahulsc/forge --skill requesting-code-review-rahulsc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the risk of merging low-quality or buggy code into the main branch by providing a structured process for code review before deployment.

Core Features & Use Cases

  • Automated Code Review Dispatch: Integrates with subagents like forge:code-reviewer and forge:security-reviewer based on risk tiers.
  • Evidence-Based Verification: Requires reviewers to provide specific file:line citations for their feedback, preventing vague assessments.
  • Use Case: Before merging a new feature, you can use this skill to automatically send the code to a designated reviewer, ensuring it meets quality standards and requirements.

Quick Start

Use the requesting-code-review skill to get the current code changes reviewed by the code-reviewer subagent.

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 before merging changes?▼

Automate code review by dispatching specialized subagents to verify code changes against defined risk tiers. This structured process requires evidence-based feedback with specific file:line citations before integration, ensuring code quality standards are met prior to deployment.

How does evidence-based code review work for feature integration?▼

Evidence-based code review requires reviewers to provide specific file:line citations for their feedback. This prevents vague assessments by mandating that every code change is verified against requirements with concrete proof before merging into the main branch.

What's the best way to handle security reviews for high-risk code deployments?▼

Handle security reviews for deployments by mandating security reviews for critical tasks through a dedicated security-reviewer subagent. This structured approach dispatches specialized reviews based on defined risk tiers to catch vulnerabilities before integration.

Do I need to define risk tiers to use a structured code review process?▼

Defining risk tiers is required for a structured code review process because the system dispatches specialized subagents based on those tiers. This ensures code changes receive the correct level of scrutiny, including mandatory security reviews for critical tasks.

Can I use team-based peer reviews with automated code verification?▼

Team-based peer reviews are supported alongside automated code verification. The process facilitates team collaboration while dispatching subagents to ensure changes are verified against requirements with specific, evidence-based feedback before integration into the main branch.

Related Skills

Explore More Software Engineering Skills→
appautomatonappautomaton
37

auto-execute

Orchestrate approved project plan slices via direct execution or subagent dispatch.

Official
Advanced
zizzfizzixzizzfizzix

code-review

Automate code review for architectural, security, and quality compliance.

Community
Advanced
kriegcloudkriegcloud
68

subagent-driven-development

Execute implementation plans by dispatching subagents with two-stage reviews.

Community
Advanced
conejoRojoconejoRojo

requesting-code-review

Dispatch a subagent to evaluate git-based changes against project requirements.

Community
Advanced