skills.rest
WesleyMFrederick
WesleyMFrederickCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Dispatch a code-reviewer subagent to review Git changes between BASE_SHA and HEAD_SHA.

Updated Oct 25, 2025
Search Tags:#git#software engineering#quality assurance#code review#developer workflow#technical debt
One-click install
npx skills add https://github.com/WesleyMFrederick/cc-workflows --skill requesting-code-review-wesleymfrederick
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/WesleyMFrederick/cc-workflows/tree/main/.claude/skills/requesting-code-review copy
Command: npx skills add https://github.com/WesleyMFrederick/cc-workflows --skill requesting-code-review-wesleymfrederick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents cascading issues, undetected bugs, and architectural drift by automating code review requests, ensuring consistent quality and reducing technical debt.

Core Features & Use Cases

  • Subagent Dispatch: Dispatches a dedicated code-reviewer subagent to perform automated code reviews.
  • Structured Review Request: Guides you in providing all necessary context (Git SHAs, implementation summary, plan) for an effective and focused review.
  • Feedback Integration: Provides a clear process for acting on critical, important, and minor feedback, ensuring issues are addressed systematically.

Quick Start

Use the requesting-code-review skill to get feedback on my latest commits for the 'user-settings' feature.

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 reviews to catch issues before merging?▼

Code review automation dispatches a dedicated reviewer to examine your Git changes systematically. It requires your base and head commit SHAs, implementation summary, and plan, then returns structured feedback on critical, important, and minor issues to fix before proceeding to merge.

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

Request code review after completing major features, before merging to main, after subagent-driven tasks, or when stuck on implementation decisions. This prevents cascading bugs, undetected issues, and architectural drift while reducing technical debt accumulation.

What information do I need to provide for an effective code review?▼

Provide your BASE_SHA and HEAD_SHA from Git, a summary of what changed and why, your implementation plan, and context about the feature or fix. This structured input focuses the review on relevant concerns and ensures actionable feedback.

How do I act on code review feedback once I receive it?▼

Address critical and important issues systematically before proceeding; minor feedback can be logged for later. Fix the identified problems, then continue with your next task or proceed to merge once all critical issues are resolved.

Can I use code review automation for refactoring work?▼

Yes. Dispatch code review before refactoring or after completing refactoring tasks to catch unintended behavioral changes, performance regressions, or architectural inconsistencies introduced during the refactor.

Related Skills

Explore More Software Engineering Skills→
gyuhagyuha
2

sg-review

Review git-changed files and write findings to SUMMARY.md and HANDOFF.md.

Community
Intermediate
kinneyyankinneyyan
2

code-review

Analyze git changes to identify critical and high-priority issues.

Community
Advanced
KaimingWanKaimingWan
103

requesting-code-review

Dispatch a code-reviewer subagent to analyze code changes against requirements.

Community
Intermediate
R2W1csR2W1cs
1

lint-and-validate

Lint and validate JavaScript and Python code for syntax and style issues.

Community
Intermediate