requesting-code-review

Dispatch a subagent to analyze code changes against project plans and requirements.

1|1|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/ntaksh42/agents --skill requesting-code-review-ntaksh42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ntaksh42/agents/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/ntaksh42/agents --skill requesting-code-review-ntaksh42

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps catch bugs and ensure code meets requirements by integrating a code review process early and often in the development lifecycle.

Core Features & Use Cases

  • Proactive Issue Detection: Identifies potential problems before they become major issues or are merged into the main codebase.
  • Requirement Verification: Ensures that implemented features align with the original plan or requirements.
  • Use Case: After completing a task to add a new verification function, you can use this Skill to have a code-reviewer subagent check your implementation against the task requirements and Git history before proceeding to the next task or merging.

Quick Start

Use the requesting-code-review skill to dispatch the code-reviewer subagent to review 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 ensure code quality before merging changes into the main branch?

To ensure code quality before merging, you can run an automated code review that analyzes your Git commits against project requirements to catch critical and minor issues early.

How do I verify my implemented features align with the original development plan?

To verify implemented features against your development plan, dispatch a code review subagent to analyze your Git history and task requirements for any deviations or missing functionality.

Can I use an automated code reviewer to check my code changes after completing a task?

Yes, you can use an automated code reviewer after task completion to check your code changes, ensuring that the implementation meets the specified requirements before you proceed to the next development phase.

What is the best way to catch bugs early in the software development workflow?

The best way to catch bugs early in the development workflow is to integrate automated code analysis that reviews code commits against project plans, detecting potential problems before they are merged into the main codebase.

Does automated code review work with my existing Git history and project requirements?

Yes, automated code review works with your existing Git history and project requirements by analyzing code changes directly against your defined plans to identify any critical or important issues.

When should I run a code review during feature implementation?

You should run a code review during feature implementation after completing a task, before proceeding to the next task, or during pre-merge verification to ensure early detection of critical and minor issues.