requesting-code-review

Coordinate structured code reviews before merging major feature changes.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/zinohome/zinoClaw --skill requesting-code-review-zinohome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/zinohome/zinoClaw/tree/main/docker-customize/deskclaw-resources/skills/requesting-code-review
Command: npx skills add https://github.com/zinohome/zinoClaw --skill requesting-code-review-zinohome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid shipping flawed implementations by coordinating focused code reviews before major changes are merged.

Core Features & Use Cases

  • Review Dispatch Guidance: Provides a structured process for requesting a code-reviewer subagent with precise implementation context.
  • Quality Assessment Framework: Defines checks for code quality, architecture, testing, requirements, and production readiness.
  • Use Case: Use this Skill after completing a major feature or before merging changes to identify critical bugs, design issues, and missing requirements.

Quick Start

Ask the code review skill to review my completed feature changes against the implementation requirements and provide a production readiness assessment.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I run a code review before merging major feature changes?

To run a pre-merge code review, you request a code-reviewer subagent with precise implementation context to evaluate code quality, architecture, testing, and requirements alignment for your completed feature changes.

What is pre-merge validation in software engineering?

Pre-merge validation is a structured code review process that evaluates implementation details, architecture, and production readiness to catch critical bugs and design issues before code changes are merged.

When do I need to request a code review for refactoring decisions?

You should request a code review for refactoring decisions and major features to identify missing requirements, evaluate code quality, and provide a production readiness assessment before the changes reach production.

Can I use a subagent to check implementation requirements and production readiness?

Yes, you can dispatch a code-reviewer subagent to assess your completed feature changes against implementation requirements, performing quality assurance checks for architecture, testing, and production readiness.

What is the best way to validate code quality before a git merge?

The best way to validate code quality before a git merge is coordinating a structured review process that applies a quality assessment framework to check implementation details, requirements alignment, and architecture.

What are the limitations of automated code review for complex refactoring?

This code review coordination requires a structured review process to evaluate implementation details and production readiness; without precise implementation context, the subagent may miss complex refactoring design issues.