skills.rest
han-so1omon
han-so1omonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Automate code reviews with a dedicated reviewer agent using a defined diff range.

1|Updated Apr 7, 2026
Search Tags:#automation#qa#subagent#developer-workflow#code-review#production-readiness#review-checklist
One-click install
npx skills add https://github.com/han-so1omon/ikam --skill requesting-code-review-han-so1omon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/han-so1omon/ikam/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/han-so1omon/ikam --skill requesting-code-review-han-so1omon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Code Review process is often inconsistent and slow, leading to undetected issues and delayed releases; this Skill provides a structured approach to prompt, thorough reviews by a dedicated reviewer agent.

Core Features & Use Cases

  • Automates production-ready code reviews by providing precise context to a dedicated reviewer agent.
  • Guides reviewers through testing, architecture, security, and readiness criteria with a structured checklist.
  • Useful after each task, after completing major features, or before merging to main, to catch issues early and preserve context.

Quick Start

Dispatch the code-reviewer subagent with the implemented changes and include a short plan and the BASE_SHA/HEAD_SHA references to generate 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 to main?▼

Automate code reviews by dispatching a reviewer subagent with a defined diff range (BASE_SHA..HEAD_SHA) and a formal plan to check code quality, architecture, testing, and production readiness.

What is a production-ready code review checklist?▼

A production-ready code review checklist systematically guides a reviewer agent through testing, architecture, security, and release criteria to catch issues early and preserve context before merging to main.

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

Run an automated code review after completing each task, finishing major features, or before merging to main to ensure release readiness and catch issues early across software development workflows.

How do I provide context to a subagent for code review?▼

Provide context to a subagent for code review by supplying the implemented changes, a short formal plan, and the BASE_SHA and HEAD_SHA references to generate a precise structured review.

Do I need a formal plan to run an automated code review?▼

Yes, a formal plan is required to run an automated code review, ensuring the dedicated reviewer agent has precise context and structured coverage of code quality and production readiness.

What are the limitations of using a subagent for code reviews?▼

The subagent code review requires a defined diff range and formal plan to function, meaning it cannot review uncommitted changes or operate without explicit production-readiness criteria.

Related Skills

Explore More Software Engineering Skills→
caitengweicaitengwei
6

requesting-code-review

Triggers Git-based code review using BASE_SHA and HEAD_SHA ranges.

Community
Intermediate
SeanHoggSeanHogg
3

prepare-pr

Rebase a GitHub Pull Request onto main, fix review findings, run gates, and push.

Community
Advanced
alffeialffei
69

requesting-code-review

Dispatch a code-reviewer subagent to validate git changes before merging.

Community
Intermediate
HenquewlHenquewl
7

requesting-code-review

Dispatch a subagent to review git-based changes across commit ranges.

Community
Intermediate