requesting-code-review

Dispatch a code-reviewer subagent to automate code review initiation and execution.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill requesting-code-review-ahmedelhadarey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/AhmedElhadarey/Gilfoyle/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill requesting-code-review-ahmedelhadarey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initiation and execution of code reviews by dispatching a dedicated code-reviewer subagent to catch issues early.

Core Features & Use Cases

  • Automated Review Triggers: Automatically request reviews after each task, major feature implementation, or before merging to main.
  • Structured Feedback: Uses templates to standardize feedback, categorize issues, and surface critical risks.
  • Use Case: Teams using task-driven development can ensure every change passes through a formal review gate before integration.

Quick Start

Trigger a code review after every task or before merging to ensure quality gates are met.

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 reviews for every task before merging to main?

Automating code reviews is achieved by dispatching a dedicated code-reviewer subagent after each task or major feature implementation. This ensures quality gates are met before integration to main by applying a standardized review template.

What is a code-reviewer subagent and how does it standardize pull request feedback?

A code-reviewer subagent is an automated agent that executes code reviews by categorizing issues and surfacing critical risks. It standardizes pull request feedback through a structured template to provide actionable insights.

When do I need to trigger a code review in a task-driven development workflow?

You need to trigger a code review in a task-driven workflow after completing each task, finishing a major feature implementation, or before merging to main. This ensures all changes pass through a formal quality gate.

Does this code review automation work without external dependencies?

Yes, this code review automation works without external dependencies. It independently initiates and executes the review process by dispatching a subagent to perform risk assessment and issue classification.

Can I use structured templates to classify code review issues and surface risks?

Yes, you can use structured templates to classify code review issues. The automated review process uses templates to standardize feedback, categorize identified issues, and surface critical risks before merging.

What's the best way to ensure quality gates are met before merging to main?

The best way to ensure quality gates are met is by automatically requesting a code review before merging to main. This dispatches a subagent to apply structured planning, risk assessment, and actionable feedback.