code-review

Dispatch code-reviewer sub-agents and process feedback with a 6-step response pattern.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Likas07/t3code-skills --skill code-review-likas07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Likas07/t3code-skills/tree/main/skills/code-review
Command: npx skills add https://github.com/Likas07/t3code-skills --skill code-review-likas07

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the entire code review process, from proactively requesting reviews to rigorously handling feedback, ensuring higher code quality and efficient collaboration.

Core Features & Use Cases

  • Proactive Review Requests: Automatically dispatch specialized sub-agents to catch issues early in the development cycle.
  • Rigorous Feedback Handling: Implements a structured 6-step pattern for evaluating and responding to feedback, emphasizing technical correctness over performative agreement.
  • Use Case: After completing a feature, you can use this skill to request a review from a code-reviewer sub-agent, then systematically address any feedback using the provided response patterns, ensuring all critical and important issues are resolved before merging.

Quick Start

Use the code-review skill to request a review for your latest changes by providing the base and head SHAs.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review requests before merging new features?

Automate code review requests by dispatching a specialized sub-agent to proactively evaluate changes. You provide the base and head SHAs to trigger the review, catching critical issues early before merging features.

What is the structured process for handling feedback during a code review?

Handling feedback follows a rigorous 6-step response pattern emphasizing technical verification and reasoned pushback. This structured protocol ensures developers evaluate issues based on technical correctness rather than performative agreement.

When should I request a code review in the development lifecycle?

Request a code review before merges, after completing tasks, or when finalizing major features. Requesting reviews at these milestones ensures continuous quality assurance and production readiness throughout the lifecycle.

Can I systematically process feedback to ensure code quality without manually tracking every comment?

Systematically process feedback using provided response patterns to address all critical and important issues. This approach ensures code quality and production readiness without manually tracking every individual comment.