skills.rest
mliudev
mliudevCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Inspect code changes and categorize findings as Critical, Important, or Minor.

Updated Apr 21, 2026
Search Tags:#subagent#quality-assurance#code-review#pull-request#diff-inspection#bounded-review
One-click install
npx skills add https://github.com/mliudev/agent-workflows --skill requesting-code-review-mliudev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/mliudev/agent-workflows/tree/main/skills/claude/requesting-code-review
Command: npx skills add https://github.com/mliudev/agent-workflows --skill requesting-code-review-mliudev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code reviews are often delayed or inconsistent; this skill provides a bounded, read-only review pass to surface issues early and guide safe shipping.

Core Features & Use Cases

  • Bounded, read-only review pass that focuses on diffs and risk signals.
  • Categorizes findings as Critical, Important, or Minor with concrete file references.
  • Supports integration with a subagent workflow to avoid manual editing during review.

Quick Start

Invoke after meaningful changes and let the subagent generate a bounded, read-only 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 perform a read-only code review on a pull request diff?▼

A read-only code review inspects pull request diffs to surface Critical, Important, and Minor findings with file references. It categorizes issues and returns actionable recommendations without modifying the code during the review.

When should I run a bounded code review on my changes?▼

Run a bounded code review after meaningful implementation slices or before opening a pull request. This surfaces risk signals early and provides a focused verification plan to guide safe shipping steps.

Can I use a subagent workflow to inspect code changes without editing files?▼

Yes, a subagent workflow supports read-only diff inspection to avoid manual editing during code review. The subagent analyzes the changes and generates bounded recommendations with fixes and deferrals.

What is the best way to categorize code review findings by severity?▼

Categorize code review findings as Critical, Important, or Minor based on risk signals in the diff. Provide concrete file references for each finding to return actionable recommendations and a focused verification plan.

Does a bounded code review automatically fix the issues it finds?▼

No, a bounded code review is strictly read-only and does not edit code during the review. It prepares findings with file references and returns recommendations for fixes and deferrals to guide next steps.

Related Skills

Explore More Software Engineering Skills→
balajivisbalajivis
2

review

Analyze Git-based code diffs to detect structural risks before merging.

Community
Advanced
JordiNodeJSJordiNodeJS

sonarqube-best-practices

Apply SonarLint severity prioritization to TypeScript code in Next.js 16 projects.

Community
Intermediate
xlelibertyxleliberty

subagent-driven-development

Orchestrates multi-task implementation plans by dispatching specialized subagents for development and review.

Community
Advanced
conejoRojoconejoRojo

requesting-code-review

Dispatch a subagent to evaluate git-based changes against project requirements.

Community
Advanced