requesting-code-review

Dispatch a code-reviewer subagent to generate structured feedback for pre-merge checks.

3|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/nassimbf/ftitos-claude-code --skill requesting-code-review-nassimbf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/nassimbf/ftitos-claude-code/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/nassimbf/ftitos-claude-code --skill requesting-code-review-nassimbf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates code-review planning and feedback by dispatching a dedicated reviewer to evaluate work artifacts before merge, helping teams catch issues early and maintain quality.

Core Features & Use Cases

  • Dispatch a code-reviewer subagent to evaluate changes with precise context and criteria.
  • Enforce early feedback on tasks, features, and major refactors before merging.
  • Generate structured feedback summaries with strengths, issues, and remediation guidance for quick action.

Quick Start

Dispatch a code-reviewer subagent after completing a task to obtain structured feedback before merging.

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 feedback before merging a feature?▼

To automate code review feedback before a merge, dispatch a dedicated reviewer subagent with implementation details, requirements, and commit SHAs to output a structured assessment for remediation.

What is a subagent code review and how does it work for task-driven development?▼

A subagent code review is an automated evaluation where a dedicated agent analyzes your artifacts using implementation context and commit ranges to generate structured feedback on strengths and issues.

What context do I need to provide for an automated pre-merge code review?▼

For an automated pre-merge code review, you must provide what was implemented, the plan or requirements, the base SHA, and the head SHA to ensure the reviewer evaluates the correct changes.

Can I use automated code review for major refactors or is it only for new features?▼

Automated code review can be used for major refactors, new features, and task-driven development to enforce early formal feedback and catch issues before merging any significant changes.

How do I get structured remediation guidance from a code review?▼

To get structured remediation guidance from a code review, dispatch the reviewer subagent with your commit details and it will output a summary containing strengths, identified issues, and actionable guidance.

When should I dispatch a code-reviewer subagent in my development workflow?▼

You should dispatch a code-reviewer subagent after completing a task, feature, or major refactor to obtain formal structured feedback and catch issues early before proceeding to a merge.