review

Review uncommitted code changes for architecture, security, and best practices.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yyiilluu/reflexio --skill review-yyiilluu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/yyiilluu/reflexio/tree/main/.claude/commands/review
Command: npx skills add https://github.com/yyiilluu/reflexio --skill review-yyiilluu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of conducting thorough code reviews, ensuring code quality, security, and adherence to best practices before changes are committed.

Core Features & Use Cases

  • Comprehensive Analysis: Analyzes architecture, code quality, security, and engineering best practices.
  • Inline Feedback: Embeds questions and assumptions directly within the review report.
  • Change Plan Proposal: Summarizes proposed changes for user approval before any edits are made.
  • Use Case: A developer finishes a new feature and wants a senior engineer's feedback. They run this Skill, which provides a detailed report and a proposed list of changes to improve the code.

Quick Start

Use the review skill to perform a rigorous code review of all uncommitted changes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a rigorous code review on uncommitted git changes?

Code review for uncommitted changes involves analyzing architecture, security, and best practices. It embeds inline questions and assumptions, then proposes a change plan for user approval before edits, automating linters and type checkers.

What does an automated code review checklist cover for security and correctness?

An automated code review checklist covers security, correctness, design, API contracts, error handling, type safety, performance, testing, duplication, and clarity to validate engineering best practices before a commit.

Can I automate linters and type checkers during a pre-commit code review?

You can automate checks including linters and type checkers during a pre-commit code review. This validates type safety and code quality, generating a detailed report and proposed refactoring changes for approval.

What is the best way to propose refactoring changes without modifying code directly?

The best way to propose refactoring changes without modifying code directly is to summarize proposed changes in a report for user approval. The review embeds inline questions and assumptions before applying any edits.

Does the code review process work without committing changes to git?

Yes, the code review process works directly on uncommitted changes in git. It analyzes your working directory for architecture and security issues, proposing a change plan for approval before any edits or commits are executed.