skills.rest
ingbyr
ingbyrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

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

2|Updated Apr 3, 2026
Search Tags:#git#subagent#quality-assurance#code-review#pull-request#review-automation
One-click install
npx skills add https://github.com/ingbyr/lzcode --skill requesting-code-review-ingbyr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ingbyr/lzcode/tree/main/packages/desktop/src-tauri/lz-assets/skills/requesting-code-review
Command: npx skills add https://github.com/ingbyr/lzcode --skill requesting-code-review-ingbyr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure code changes are reviewed early and thoroughly before merge by routing focused context to a dedicated code-reviewer subagent.

Core Features & Use Cases

  • Dispatch a focused code-reviewer subagent with the exact change summary to surface issues early.
  • Provide a clear plan and requirements reference to align reviewer feedback with the intended outcome.
  • Capture structured feedback, categorize issues by severity, and decide readiness for merge.

Quick Start

Dispatch the code-reviewer subagent with your change summary and plan to start the 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 a code review before a pull request merge?▼

Automating a pre-merge code review involves dispatching a focused subagent with your change summary, plan, and git SHAs to evaluate readiness. This skill routes that context to generate structured feedback and categorize issues by severity before production.

What do I need to provide to run a pre-merge code review check?▼

Pre-merge code review checks require the WHAT_WAS_IMPLEMENTED summary, PLAN_OR_REQUIREMENTS, BASE_SHA, and HEAD_SHA. Supplying these inputs allows the reviewer subagent to align feedback with intended outcomes and evaluate the exact code changes.

How does a subagent evaluate code changes for production readiness?▼

A subagent evaluates production readiness by comparing the provided base and head git SHAs against the implementation plan. It captures structured feedback, categorizes issues by severity, and outputs a merge readiness decision.

Can I get structured code review feedback for task-driven development?▼

Structured code review feedback for task-driven development is generated by providing the subagent with the specific change summary and requirements. The subagent surfaces issues early and categorizes them by severity to ensure alignment with the intended outcome.

When should I use an automated code reviewer for feature implementation?▼

Automated code reviewers should be used for feature implementations when critical feedback is needed before merging. Dispatching a dedicated subagent ensures code changes are reviewed early and thoroughly by routing focused context to evaluate readiness.

Related Skills

Explore More Software Engineering Skills→
miles990miles990

requesting-code-review

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

Community
Intermediate
peancharoenpeancharoen

speckit.reviewer

Review git diffs and file paths for code issues with severity labels.

Community
Intermediate
the-inconvenience-storethe-inconvenience-store
1

requesting-code-review

Manage code review requests and track reviewer feedback with git and Dolt.

Community
Intermediate
kitfunsokitfunso

requesting-code-review

Dispatch a code-review subagent to categorize issues by severity before merging.

Community
Advanced