skills.rest
MacroMan5
MacroMan5COMMUNITY
Explore all skills by this author →
GitHub

code-review-request

Generate structured code review requests with findings tables and patch plans.

Updated Aug 27, 2026
Search Tags:#quality assurance#code review#feedback#development workflow#pull request#patch plan
One-click install
npx skills add https://github.com/MacroMan5/claude-code-workflow-plugins --skill code-review-request
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-request
Source: https://github.com/MacroMan5/claude-code-workflow-plugins/tree/main/.claude/skills/code-review-request
Command: npx skills add https://github.com/MacroMan5/claude-code-workflow-plugins --skill code-review-request

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code review requests often lack structure, making it hard for reviewers to provide focused feedback and for developers to act on it efficiently.

Core Features & Use Cases

  • Structured Summary: Automatically summarizes changes, their purpose, and potential risks in a concise bulleted list.
  • Table-Based Rubric: Generates a clear table of findings, including issue, severity (Critical/Warning/Suggestion), file:line, and a proposed fix plan.
  • Use Case: After implementing a task and passing local quality checks, use this skill to generate a structured code review request, highlighting key changes and potential risks, ready for your team.

Quick Start

Request a code review for the recent changes in 'src/auth/user_service.py' and its associated tests.

Frequently Asked Questions about code-review-request

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

FAQPage Schema
How do I structure code review feedback with severity levels and actionable fixes?▼

Code review requests can be structured using a table-based rubric that categorizes findings by severity (Critical, Warning, Suggestion), includes file:line references, and proposes specific fixes. This approach ensures reviewers provide focused feedback and developers can act on it systematically.

When should I request a code review in my development workflow?▼

Request a code review after your changes pass local quality checks but before committing or opening a pull request. This timing lets you incorporate structured feedback early and reduce revision cycles on the actual PR.

Can code review requests generate pull request-ready comments?▼

Yes, code review requests can optionally produce PR-ready comments that summarize changes, highlight risks, and include the rubric findings—ready to post directly without manual reformatting.

Does this approach work with existing pull request workflows?▼

Code review requests integrate into PR workflows by generating structured feedback before submission. They don't auto-commit changes; instead, they propose diffs and a patch plan for you to review and apply manually.

What output do I get from a code review request?▼

You receive a summary of changes and their purpose, a table of findings organized by severity with file:line locations, and a 3–6 step patch plan to address issues systematically.

Do I need to manually commit changes after getting code review feedback?▼

Yes, code review requests enforce no auto-commits. They propose diffs and patches for your review, but you control when and how to apply changes and commit them yourself.

Related Skills

Explore More Software Engineering Skills→
cartridge-ggcartridge-gg
80

validate-before-merge

Run lint, build, and test checks before merging code.

Official
Advanced
a-taka-tak
1

git-create-pr

Commit changes, push to origin, and create a GitHub Pull Request.

Community
Intermediate
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
Luney-IndustriesLuney-Industries
4

address-pr-comments

Categorize GitHub pull request comments and generate action plans.

Official
Advanced