code-review

Review git-backed code changes and report findings by severity.

32|6|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/flc1125/skills --skill code-review-flc1125
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/flc1125/skills/tree/main/skills/code-review
Command: npx skills add https://github.com/flc1125/skills --skill code-review-flc1125

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of reviewing code changes, ensuring quality and adherence to requirements before integration.

Core Features & Use Cases

  • Scoped Code Reviews: Define specific git SHA ranges for focused analysis.
  • Contextual Summarization: Provide implementation details and requirements for reviewers.
  • Review Delegation/Execution: Dispatch to a dedicated reviewer or perform the review in-session.
  • Severity-Based Reporting: Output findings categorized by Critical, Important, and Minor issues.
  • Use Case: After completing a new feature, use this Skill to generate a review request for your team, summarizing the changes and requirements, and ensuring all critical issues are addressed before merging.

Quick Start

Use the code-review skill to review the changes between the commits abc1234 and def5678.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review code changes between two specific git commits?

Define a review scope using specific git SHA ranges to perform a focused code review. The skill analyzes git diff and log data to summarize implementation context and report findings by severity.

Can I delegate a code review to a subagent instead of doing it myself?

Yes, you can delegate a code review to a dedicated subagent or perform the review directly in-session. Both methods generate a structured findings template reporting issues by severity.

How does severity-based reporting work for code review findings?

Severity-based reporting categorizes code review findings into Critical, Important, and Minor issues. This structured findings template ensures reviewers address critical defects before merging.

Do I need a local git repository to run a scoped code review?

Yes, you need a local git repository because the code review relies on git commands for diff and log analysis. These commands extract the implementation context and requirements needed for the review.

What is the best way to summarize implementation context for a code review request?

The best way to summarize implementation context is providing the git SHA range and requirements. This scopes the review and allows the skill to extract logs and diffs for the reviewer.