skills.rest
makerjackie
makerjackieCOMMUNITY
Explore all skills by this author →
𝕏@maker_jackieGitHub

requesting-code-review

Dispatch a code-review subagent to review changes against a spec.

Updated Feb 20, 2026
Search Tags:#automation#git#subagent#code-review#pull-request#review-process
One-click install
npx skills add https://github.com/makerjackie/jackie-skills-cn-top50 --skill requesting-code-review-makerjackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/makerjackie/jackie-skills-cn-top50/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/makerjackie/jackie-skills-cn-top50 --skill requesting-code-review-makerjackie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates early, structured code review by dispatching a dedicated code-review subagent to catch issues before they cascade.

Core Features & Use Cases

  • Mandatory review after each task in subagent-driven development to ensure quality.
  • Clear workflow: capture base/head SHAs, dispatch subagent with a review plan, and act on feedback.
  • Example scenario: before merging a feature branch, trigger a code-review to validate changes against the spec.

Quick Start

Dispatch the code-reviewer subagent after finishing a task, providing the required placeholders to initiate a review.

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 before merging a pull request?▼

Automate code reviews by dispatching a dedicated code-review subagent to catch issues early before merging. It enforces review discipline by validating changes against the spec after each task and before merging to main.

What is subagent-driven code review and how does it work?▼

Subagent-driven code review dispatches a dedicated reviewer subagent to assess changes against a spec. It works by capturing base and head SHAs and providing a clear description and plan so the reviewer can evaluate.

When do I need to trigger an automated code review in my workflow?▼

Trigger an automated code review after each task in subagent-driven development, after completing major features, and before merging to main. This enforces review discipline and catches issues early.

How to capture base and head SHAs to initiate a subagent code review?▼

Capture the base and head SHAs from your Git branch and provide them with a clear description and plan to the code-reviewer subagent. This provides the required context to initiate a review and assess changes against the spec.

Do I need a clear description and plan for the code-review subagent to work?▼

Yes, you need a clear description and plan for the code-review subagent to work. Providing this context is required so the reviewer subagent can accurately assess your changes against the original specification.

Related Skills

Explore More Software Engineering Skills→
Neroro64Neroro64

requesting-code-review

Dispatch a code-reviewer subagent with task context for pre-merge checks.

Community
Advanced
sachio222sachio222

requesting-code-review

Route code changes to a dedicated code-reviewer subagent for pre-merge quality validation.

Community
Advanced
Monjyu1101Monjyu1101
1

requesting-code-review

Automate pre-commit code verification with security scans, quality gates, and auto-fixes.

Community
Advanced
froggugugugufroggugugugu

code-review

Review code changes for quality, conventions, performance, and security.

Community
Advanced