review

Review code changes with auto-detected scope and focused checklists.

1|Updated Feb 5, 2026

Search Tags:#ui #architecture #checklist #style #data #quality #code-review

Ready to run

npx skills add https://github.com/eygraber/jellyfin-kmp --skill review-eygraber

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/eygraber/jellyfin-kmp/tree/main/.claude/skills/review
Command: npx skills add https://github.com/eygraber/jellyfin-kmp --skill review-eygraber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool streamlines code reviews by providing structured, comprehensive checklists across UI, architecture, data, quality, and style, ensuring consistent feedback and higher-quality code.

Core Features & Use Cases

Auto-detects scope from staged changes or commits to focus the review.
Applies explicit focus areas such as ui, domain, data, architecture, quality, style, and docs.
Composes targeted review checklists and guides reviewers through a thorough evaluation of changes.
Supports multi-area reviews (e.g., "ui architecture" or "data quality") and file-specific focus.
Documents the review process, the rationale, and actionable improvements for maintainers.

Quick Start

Provide a code review using the default auto-detect scope or specify a focus like '/review ui MyFile.kt' to constrain the checklist.

Frequently Asked Questions about review

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

FAQPage Schema

How do I perform a comprehensive code review across multiple areas like UI and architecture?▼

Perform a comprehensive code review by applying structured checklists across UI, architecture, data, quality, and style areas. This ensures consistent feedback by guiding reviewers through a thorough evaluation of code changes using multi-area focus.

Can I auto-detect the scope of my code review from git changes?▼

Yes, you can auto-detect the scope of your code review from git changes. The tool automatically analyzes staged changes or commits to focus the review and compose targeted checklists without requiring manual area specification.

How do I focus a code review checklist on a specific file and domain?▼

Focus a code review checklist on a specific file and domain by specifying the area and file path, such as '/review ui MyFile.kt'. This constrains the checklist to evaluate only the targeted domain and file-specific changes.

What is the best way to ensure consistent code quality and style during PR reviews?▼

Ensure consistent code quality and style during PR reviews by applying dedicated quality and style checklists. These structured checklists guide reviewers through evaluating changes systematically, resulting in higher-quality code and consistent feedback.

Does this code review tool support evaluating documentation and data changes?▼

Yes, this code review tool supports evaluating documentation and data changes. It implements specific docs and data checklists to assess these areas alongside UI, architecture, domain, quality, and style during the review process.