requesting-code-review

Orchestrate structured code reviews using Base and Head SHAs.

Updated Nov 8, 2024

Search Tags:#automation #workflow #subagent #quality-assurance #code-review #git-diff

Ready to run

npx skills add https://github.com/cqkxxc/cqkxxc.github.io --skill requesting-code-review-cqkxxc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/cqkxxc/cqkxxc.github.io/tree/main/.trae/skills/requesting-code-review
Command: npx skills add https://github.com/cqkxxc/cqkxxc.github.io --skill requesting-code-review-cqkxxc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and enforces early, formal code reviews to catch issues before they cascade, reducing risk in task-driven and feature-driven development.

Core Features & Use Cases

Standardizes when to request review (after each task, after major feature, before merge)
Guides reviewers through structured feedback across code quality, architecture, testing, and readiness
Supports ad-hoc reviews and integration with subagent workflows for collaborative improvement

Quick Start

Dispatch the code-reviewer subagent with the change summary and the Base and Head SHAs to begin the formal 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 code review before merging to main?▼

Automate code review by dispatching a code-reviewer subagent with Base and Head SHAs and a change summary to generate a diff-based production-readiness assessment with categorized issues.

When should I request a code review in subagent-driven development?▼

Request a code review after completing each task, finishing major features, or before merging to main to catch issues early. Optional reviews can also be triggered when stuck or refactoring.

What inputs are required to run a structured code review workflow?▼

Structured code review requires Base and Head SHAs, a concise description of what was implemented, and a plan or requirements reference to evaluate the diff and produce categorized feedback.

How does a formal code review assess production readiness?▼

Formal code review assesses production readiness by guiding reviewers through structured feedback across code quality, architecture, testing, and readiness, outputting a diff-based assessment with categorized issues.

Can I request a code review when stuck on a refactoring task?▼

Yes, you can request a code review when stuck or refactoring. Dispatch the code-reviewer subagent with the change summary and Base and Head SHAs to receive structured feedback and collaborative improvement suggestions.

Does subagent-driven code review work without external dependencies?▼

Yes, subagent-driven code review works without external dependencies. It orchestrates a structured code-reviewer workflow internally to enforce early, formal reviews and reduce risk in task-driven and feature-driven development.