requesting-code-review

Name: requesting-code-review
Availability: InStock
Author: Kaivy

Dispatch a subagent to analyze git diffs and categorize issues by severity.

20|7|Updated Feb 11, 2026

Search Tags:#git #testing #quality assurance #code review #development workflow #subagent

Ready to run

npx skills add https://github.com/kaivyy/kabot --skill requesting-code-review-kaivyy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/kaivyy/kabot/tree/main/kabot/skills/requesting-code-review
Command: npx skills add https://github.com/kaivyy/kabot --skill requesting-code-review-kaivyy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring that code changes are thoroughly checked for quality, adherence to requirements, and potential issues before being merged, thereby preventing bugs and maintaining project integrity.

Core Features & Use Cases

Automated Code Analysis: Dispatches a specialized subagent to review code against defined requirements and best practices.
Severity-Based Feedback: Categorizes identified issues into Critical, Important, and Minor for prioritized action.
Use Case: After implementing a new user authentication module, you can use this Skill to have an AI reviewer check the code for security vulnerabilities, adherence to the original plan, and test coverage before merging it into the main branch.

Quick Start

Use the requesting-code-review skill to dispatch the code-reviewer subagent for the current commit range.

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 for git changes before merging?▼

Automate code review by dispatching a specialized subagent to analyze git diffs against implementation plans, categorizing identified issues by severity to ensure production readiness before merging.

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

Categorize code review issues by severity into Critical, Important, and Minor classifications to prioritize action on critical and important feedback before merging changes into the main branch.

How do I use git diff analysis to check code against quality standards?▼

Use git diff analysis by defining base and head SHAs to review code changes, dispatching an automated subagent to check the diff against defined requirements and quality standards.

Can I check code for security vulnerabilities and test coverage automatically?▼

Yes, you can dispatch an automated subagent to review implemented modules for security vulnerabilities, adherence to the original plan, and test coverage before merging into the main branch.

Do I need to define base and head SHAs for automated code analysis?▼

Yes, defining base and head SHAs is required to establish the commit range for git diff analysis, enabling the subagent to accurately identify and categorize code changes.