skills.rest
cinjoff
cinjoffCOMMUNITY
Explore all skills by this author →
Website𝕏@c1njoffGitHub

requesting-code-review

Dispatch a subagent to analyze code changes against requirements and quality standards.

1|2|Updated Mar 6, 2026
Search Tags:#git#quality assurance#code review#development workflow#bug detection#merge verification
One-click install
npx skills add https://github.com/cinjoff/fhhs-skills --skill requesting-code-review-cinjoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/cinjoff/fhhs-skills/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/cinjoff/fhhs-skills --skill requesting-code-review-cinjoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of getting your code reviewed, catching potential issues early and ensuring it meets requirements before merging, thus preventing bugs and improving overall code quality.

Core Features & Use Cases

  • Automated Code Review Dispatch: Integrates with a code-reviewer subagent to analyze code changes.
  • Severity-Based Feedback: Categorizes issues into Critical, Important, and Minor for prioritized action.
  • Workflow Integration: Designed to be used after tasks, feature completion, or before merges in various development workflows.
  • Use Case: After completing a new feature, you can use this skill to automatically send your changes to a code reviewer agent, get feedback on potential bugs or architectural flaws, fix them, and then proceed with merging to the main branch.

Quick Start

Use the requesting-code-review skill to dispatch a code-reviewer subagent for your latest changes.

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 a branch?▼

To automate code review before merging, you can dispatch a code-reviewer subagent to analyze your changes. This process requires providing git SHAs for base and head commits to define the review scope and catch issues early.

What is severity-based feedback in an automated code review?▼

Severity-based feedback in automated code review categorizes identified issues into Critical, Important, and Minor levels. This categorization helps you prioritize bug fixes and architectural flaws before finalizing your development workflow.

Do I need git commits to run an automated code review?▼

Yes, you need git commits to run this automated code review. The skill requires specific git SHAs for both base and head commits to accurately define the scope of the code changes being evaluated.

When should I integrate automated code review into my development workflow?▼

You should integrate automated code review into your development workflow after task completion or feature implementation. This timing ensures early detection of bugs and adherence to specifications before merging into the main branch.

Can automated code review detect architectural flaws and specification deviations?▼

Yes, automated code review can detect architectural flaws and specification deviations. By analyzing code changes against requirements and quality standards, it identifies potential bugs and structural issues across your development workflow.

Related Skills

Explore More Software Engineering Skills→
MeechYourGoalsMeechYourGoals
2

requesting-code-review

Dispatch a code-reviewer subagent to identify issues between Git commit SHAs.

Community
Intermediate
ucirelloucirello
2

requesting-code-review

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

Community
Intermediate
helix4uhelix4u

requesting-code-review

Dispatch a subagent to review code quality and correctness.

Community
Intermediate
smriksmrik
1

requesting-code-review

Dispatch an AI subagent to review code diffs against requirements.

Community
Intermediate