requesting-code-review

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

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/dwalleck/kiro-starter-kit --skill requesting-code-review-dwalleck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/dwalleck/kiro-starter-kit/tree/main/.kiro/skills/requesting-code-review
Command: npx skills add https://github.com/dwalleck/kiro-starter-kit --skill requesting-code-review-dwalleck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring that code changes are high-quality, meet requirements, and are production-ready before being merged. It helps catch bugs, architectural issues, and compliance problems early.

Core Features & Use Cases

  • Automated Code Analysis: Leverages a code-reviewer subagent to analyze code quality, architecture, testing, and requirement adherence.
  • Severity-Based Feedback: Categorizes issues into Critical, Important, and Minor for prioritized action.
  • Use Case: After implementing a new feature, you can use this Skill to automatically get a detailed review of your changes, identifying potential bugs or areas for improvement before submitting a pull request.

Quick Start

Use the requesting-code-review skill to get feedback on 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 changes to production?▼

Automating code review before merging involves dispatching a specialized subagent to analyze changes against defined requirements, categorizing issues by severity into Critical, Important, and Minor for prioritized action.

Can I integrate automated code analysis into iterative development workflows?▼

Yes, automated code analysis supports iterative development workflows by integrating reviews after each task or feature completion, ensuring continuous quality checks before merging to production.

What do I need to set up automated code analysis for git changes?▼

Automated code analysis for git changes requires git commands for SHA retrieval and a templated markdown file to define the review parameters for the code-reviewer subagent.

How does severity-based feedback work in code reviews?▼

Severity-based feedback in code reviews categorizes identified issues into Critical, Important, and Minor levels, allowing developers to prioritize fixes for bugs, architectural issues, and compliance problems efficiently.

When do I need to run a code review on my latest feature implementation?▼

You need to run a code review after implementing a new feature and before submitting a pull request, ensuring the changes are production-ready and meet all defined best practices and requirements.

What is the best way to catch architectural issues before a pull request?▼

The best way to catch architectural issues before a pull request is leveraging a code-reviewer subagent to analyze code quality and requirement adherence, catching bugs and compliance problems early.