requesting-code-review

Review code changes against quality and security checklists before merging.

Updated Sep 1, 2021
One-click install
npx skills add https://github.com/unclehowell/unclehowell --skill requesting-code-review-unclehowell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/unclehowell/unclehowell/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/unclehowell/unclehowell --skill requesting-code-review-unclehowell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents defects, security gaps, and quality regressions from reaching production by enforcing a systematic review process before code is merged.

Core Features & Use Cases

  • Self‑Review Checklist: Automated verification of conventions, tests, secrets, and debug artifacts.
  • Context Gathering: Retrieves changed files, diff summaries, and recent commits.
  • Reviewer Subagent Dispatch: Sends a focused reviewer with a detailed checklist and receives structured feedback.
  • Feedback Handling: Categorizes issues as critical, important, or minor and drives corrective actions.
  • Integration: Works seamlessly with subagent‑driven development, test‑driven development, and plan‑writing workflows.

Quick Start

Run the code review skill to evaluate my recent changes before merging.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I perform a code review before merging changes?

To perform a code review before merging, dispatch a reviewer subagent with a checklist to evaluate changed files, verify test suite execution, and categorize feedback into critical, important, or minor issues for correction.

What is a self-review checklist for code changes?

A self-review checklist is an automated verification of coding conventions, tests, secrets, and debug artifacts. It ensures changes meet quality and security standards before code is merged into the repository.

When do I need to run a code review in subagent-driven development?

You need to run a code review in subagent-driven development after completing tasks, major features, or bug fixes, and before merging code. This enforces a systematic review process to prevent quality regressions.

How does a reviewer subagent handle code review feedback?

A reviewer subagent handles code review feedback by categorizing identified issues as critical, important, or minor. It sends structured feedback based on a detailed checklist to drive necessary corrective actions.

Does this code review process work with test-driven development?

Yes, this code review process works seamlessly with test-driven development and plan-writing workflows. It requires test suite execution and retrieves recent commits to evaluate changes against quality standards.