skills.rest
acho1833
acho1833COMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Prepare code review requests with commit ranges and implementation summaries.

Updated Dec 22, 2025
Search Tags:#git#quality assurance#code review#development workflow#subagent#merge readiness
One-click install
npx skills add https://github.com/acho1833/spreadline2 --skill requesting-code-review-acho1833
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/acho1833/spreadline2/tree/main/.claude/commands/requesting-code-review
Command: npx skills add https://github.com/acho1833/spreadline2 --skill requesting-code-review-acho1833

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify completed work before it ships, reducing the risk of bugs, requirement mismatches, and avoidable rework.

Core Features & Use Cases

  • Early Review Requests: Use after finishing a task, major feature, or bug fix to catch issues while they are still cheap to resolve.
  • Subagent-Based Code Review: Dispatch a code-reviewer subagent with the relevant commit range and implementation summary.
  • Production Readiness Checks: Evaluate code quality, architecture, testing, requirements coverage, and merge readiness.
  • Use Case: After implementing a new feature, ask this Skill to prepare the review request and checklist so another agent can assess the change before merge.

Quick Start

Ask the skill to prepare a code review request for the latest completed change and include the relevant base and head commits.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a code review request for completed implementation work?▼

A code review request requires identifying the git commit range, summarizing the implementation work completed, and aligning a review checklist to evaluate code quality, testing, and merge readiness before dispatching a subagent.

When should I request a code review during the development workflow?▼

You should request a code review after completing a task, major feature, bug fix, or refactoring checkpoint to catch issues early and reduce the risk of requirement mismatches and avoidable rework before merging.

What is subagent-based code review and how does it work?▼

Subagent-based code review dispatches a code-reviewer subagent with the relevant commit range and implementation summary to evaluate code quality, architecture, testing coverage, and merge readiness against production standards.

Can I use this code review process for pre-merge verification of bug fixes?▼

Yes, this code review process supports pre-merge verification for bug fixes and refactoring checkpoints by organizing implementation summaries and commit ranges to assess changes against requirements before shipping.

What do I need to identify before generating a production readiness checklist?▼

You need to identify the git commit range and provide an implementation summary so the production readiness checklist can evaluate code quality, architecture, testing, and requirements coverage for merge readiness.

Related Skills

Explore More Software Engineering Skills→
imMamdouhaboammarimMamdouhaboammar

lesson-learned

Analyze git history and diffs to extract engineering lessons and design principles.

Community
Intermediate
fartmonarchfartmonarch
1

requesting-code-review

Review completed code changes against requirements and commit ranges.

Community
Intermediate
woxiangyangzhimaowoxiangyangzhimao
3

subagent-driven-development

Orchestrate parallel subagent tasks with spec and code quality reviews.

Community
Advanced
mortenbroesbymortenbroesby
1

requesting-code-review

Dispatch a code-reviewer subagent to evaluate code quality, architecture, testing, and production readiness.

Community
Intermediate