skills.rest
ImL1s
ImL1sCOMMUNITY
Explore all skills by this author →
Website𝕏@l1s_aiGitHub

requesting-code-review

Automates pre-merge quality checks by dispatching a code-reviewer subagent to validate changes against the project plan.

6|Updated Apr 23, 2026
Search Tags:#automation#workflow#merge#quality-assurance#task-management#code-review
One-click install
npx skills add https://github.com/ImL1s/flutter-claude-skills --skill requesting-code-review-iml1s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ImL1s/flutter-claude-skills/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/ImL1s/flutter-claude-skills --skill requesting-code-review-iml1s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review coordination is automated to verify implementations align with plans before proceeding, reducing defects and rework.

Core Features & Use Cases

  • Dispatches a code-reviewer subagent after each task or before merging to main to surface issues early.
  • Compares changes against the project plan and documents findings with severity levels.
  • Integrates with existing development workflows, enabling ad-hoc reviews during feature development and releases.

Quick Start

Dispatch the reviewer after each task to validate work against the plan and capture actionable feedback.

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 pre-merge code reviews to ensure quality?▼

Automating pre-merge code reviews is done by dispatching a code-reviewer subagent to validate implemented changes against your project plan. This produces structured feedback, severity categorization, and a formal review report to reduce defects and rework.

What is the best way to validate task implementations against a project plan?▼

Validating task implementations against a project plan is best handled by dispatching a code-reviewer subagent. It compares recent changes against planned requirements to surface issues early and document findings with severity levels.

When do I need to run a formal code review during the development workflow?▼

You need to run a formal code review after each task, during major feature work, or before merging to main. This applies across ad-hoc development, planned releases, and bug-fix cycles to ensure production readiness.

Can I integrate automated code reviews into ad-hoc feature development?▼

Yes, you can integrate automated code reviews into ad-hoc feature development and planned releases. The reviewer subagent coordinates with existing workflows to validate work and capture actionable feedback on the fly.

How does automated code review handle risk assessment and task traceability?▼

Automated code review handles risk assessment and task traceability by comparing changes against the project plan and producing a formal review report. It categorizes findings by severity levels to satisfy production readiness requirements.

Related Skills

Explore More Software Engineering Skills→
gopforevergopforever

code_review

Spawn an architect subagent to analyze code changes and plan debugging strategies.

Community
Intermediate
peancharoenpeancharoen

speckit.reviewer

Review git diffs and file paths for code issues with severity labels.

Community
Intermediate
dsifrydsifry
60

subagent-driven-development

Dispatch fresh subagents for each task and review code between tasks.

Community
Advanced
Donaldshen27Donaldshen27

subagent-driven-development

Orchestrate subagent-driven development by dispatching per-task agents with code-review checkpoints.

Community
Advanced