skills.rest
jmduea
jmdueaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Request code reviews for recent changes using Git SHAs and a subagent template.

Updated Feb 12, 2026
Search Tags:#automation#git#subagent#code-review#pull-request#review-workflow
One-click install
npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill requesting-code-review-jmduea
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/jmduea/emotiv-cortex-rs/tree/main/.github/skills/requesting-code-review
Command: npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill requesting-code-review-jmduea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures that code changes are reviewed early and often, catching defects and design issues before they reach main or production.

Core Features & Use Cases

  • When to request: after each task, upon completing major features, or before merging to main.
  • How to request: automatically gather base and head Git SHAs, then dispatch a code-reviewer subagent using a predefined template.
  • Integration: fits into sub‑agent‑driven development workflows, batch plan executions, and ad‑hoc review scenarios.
  • Red‑flag guidance: lists actions that must never be ignored, such as fixing critical issues and properly handling reviewer dissent.

Quick Start

Run the requesting-code-review skill to dispatch a code-reviewer subagent for the changes between your current HEAD and the previous commit.

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

Automate code reviews for recent git changes by gathering base and head Git SHAs and dispatching a code-reviewer subagent. This structured review workflow generates feedback automatically, ensuring changes are checked before reaching main or production.

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

Request a code review after completing a specific task, finishing a major feature implementation, or before merging to main. Early and frequent reviews catch design issues and defects before they reach production environments.

How does the subagent code review process work with git commits?▼

The subagent code review process works by identifying the Git SHAs between your current HEAD and a previous commit, then applying a predefined template to generate structured feedback on the differences.

Can I integrate automated pull request reviews into batch plan executions?▼

Yes, you can integrate automated pull request reviews into batch plan executions. The review workflow fits into sub-agent-driven development workflows and ad-hoc review scenarios without requiring additional dependencies.

What are the limitations or precautions when using a subagent for code reviews?▼

A key limitation is that you must never ignore red-flag guidance, such as fixing critical issues identified in the review and properly handling reviewer dissent, to ensure code quality is actually maintained.

Related Skills

Explore More Software Engineering Skills→
pascallammerspascallammers
1

requesting-code-review

Dispatch a code-reviewer subagent to verify implementations against project plans.

Community
Intermediate
kimprobablykimprobably

requesting-code-review

Dispatch a code reviewer subagent with crafted context for validation.

Community
Intermediate
BinyaminEdenBinyaminEden
26

requesting-code-review

Dispatch a reviewer subagent to categorize code defects by severity.

Community
Intermediate
yanochka11yanochka11

github-code-review

Review GitHub pull requests and local git diffs for defects and security issues.

Community
Advanced