skills.rest
ninjasitm
ninjasitmCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Automate production-readiness checks by delegating code review to a subagent.

2|1|Updated Dec 9, 2025
Search Tags:#automation#workflow#subagent#quality-assurance#code-review#pull-request#git-sha
One-click install
npx skills add https://github.com/ninjasitm/ai-assisted-dev-toolkit --skill requesting-code-review-ninjasitm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ninjasitm/ai-assisted-dev-toolkit/tree/main/src/monorepo/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/ninjasitm/ai-assisted-dev-toolkit --skill requesting-code-review-ninjasitm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures production readiness by automating and standardizing code review, catching issues early before they cascade.

Core Features & Use Cases

  • Trigger after each task, after major features, and before merge to enforce a review gate.
  • Use a dedicated code-reviewer subagent to systematically assess changes and provide actionable feedback.
  • Integrate with existing Git workflows by supplying BASE_SHA and HEAD_SHA and a structured feedback template.
  • Optional usage to get fresh perspectives during refactoring or when blockers occur.

Quick Start

Dispatch the code-reviewer subagent after completing a task, provide the base and head SHAs, and review the generated feedback before proceeding.

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 a git merge?▼

Automated code review before a merge is handled by dispatching a dedicated subagent using the base and head git SHAs to systematically assess changes and provide actionable feedback.

What is the best way to standardize pull request feedback?▼

Standardizing pull request feedback involves using a structured review template with explicit feedback severity to ensure consistent, traceable code quality assessments across your team.

When should I trigger an automated code review?▼

Automated code review should be triggered after every task, after major feature completion, and before merging, with optional reviews when you are stuck or refactoring.

Can I use a subagent to review code changes when I am stuck?▼

Yes, dispatching a code-reviewer subagent when stuck or refactoring provides a fresh perspective to systematically assess changes and generate actionable feedback.

How do I capture git SHAs for a structured code review?▼

Capturing git SHAs for a structured code review requires enforcing a protocol to supply the BASE_SHA and HEAD_SHA, integrating with existing Git workflows to track changes accurately.

Does automated code review work without external dependencies?▼

Yes, the automated code review subagent operates with zero dependencies, enforcing its own protocol to capture SHAs and generate structured feedback without requiring external components.

Related Skills

Explore More Software Engineering Skills→
TumeloRamaphosaTumeloRamaphosa

requesting-code-review

Request automated code review for a git change range before merging.

Community
Intermediate
bonnguyenitcbonnguyenitc
19

requesting-code-review

Review code changes in a git range and output file:line feedback with a merge verdict.

Community
Intermediate
vrcmsvrcms
1

verification-loop

Execute build, type, lint, test, and security checks in a verification pipeline.

Community
Advanced
giosuetedeschi-specgiosuetedeschi-spec

requesting-code-review

Dispatch a subagent to evaluate git diffs against project requirements.

Community
Advanced