skills.rest
brmatola
brmatolaCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Dispatch a code-reviewer subagent to review changes before merging.

Updated Jan 17, 2026
Search Tags:#subagent#quality-assurance#code-review#development-process#production-readiness#gremlins#merge-review
One-click install
npx skills add https://github.com/brmatola/gremlins --skill requesting-code-review-brmatola
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/brmatola/gremlins/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/brmatola/gremlins --skill requesting-code-review-brmatola

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures code changes are reviewed for quality and alignment before merging.

Core Features & Use Cases

  • Structured reviews: Dispatch a gremlins:code-reviewer subagent to catch issues before they cascade.
  • Plan-aligned feedback: Verify changes against the current plan and requirements.
  • Production readiness: Ensure reviews address risk, documentation, and testing needs before merge.

Quick Start

After completing a task, trigger the code-review process by dispatching the gremlins:code-reviewer subagent and providing the necessary context: WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION.

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 changes to the main branch?▼

Automate code reviews by dispatching a code-reviewer subagent after completing major features. This enforces a standardized review workflow to catch quality issues and verify alignment before merging.

What is the best way to ensure production readiness after a subagent task?▼

Ensure production readiness by triggering a code review process that verifies changes against current requirements. This addresses risk, documentation, and testing needs before any merge occurs.

How do I verify that code changes align with the original development plan?▼

Verify code changes align with your plan by providing the PLAN_OR_REQUIREMENTS alongside the BASE_SHA and HEAD_SHA. The reviewer subagent uses this context to generate structured, plan-aligned feedback.

What context do I need to provide to trigger a structured code review?▼

Provide WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION. This context allows the code-reviewer subagent to evaluate the changes accurately and capture structured feedback.

Can I use this code review process to catch issues before they cascade in development?▼

Yes, dispatching a code-reviewer subagent catches issues before they cascade. It enforces a standardized review workflow applied after every subagent task or before main branch merges.

When should I initiate a code review during the development process?▼

Initiate a code review after every subagent task, after completing major features, or before merges to the main branch. This ensures quality and alignment are checked at critical development stages.

Related Skills

Explore More Software Engineering Skills→
seanGSISGseanGSISG
3

requesting-code-review

Dispatch a code-reviewer subagent with Git SHAs and implementation details.

Community
Basic
equaltoaiequaltoai
3

implement-milestone

Orchestrate a milestone from feature branch through CI verification and merge to main.

Official
Advanced
jnealey88jnealey88
12

requesting-code-review

Trigger code reviews after each task or feature in subagent-driven workflows.

Community
Intermediate
conejoRojoconejoRojo

requesting-code-review

Dispatch a subagent to evaluate git-based changes against project requirements.

Community
Advanced