code-review

Route code reviews to specialized skills by detecting language, framework, and concern.

2|Updated Feb 12, 2024

Search Tags:#diff analysis #code review #routing #pull requests #simplification #framework detection

Ready to run

npx skills add https://github.com/adibfirman/dotfiles --skill code-review-adibfirman

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of getting the most relevant review guidance by automatically identifying the language, framework, and review focus so you don’t waste time reading generic feedback.

Core Features & Use Cases

Language- and framework-aware routing: Chooses specialized skills based on the code ecosystem (for example, Go, React web, React Native, or component composition concerns).
Diff/PR/branch review workflows: Works when you review pasted snippets, selected files, git diffs, PRs, branches, or specific repository areas.
Over-engineering cleanup enablement: Detects when simplification of verbosity, redundant checks, or “slop” is the main concern and routes to the dedicated simplification skill.

Quick Start

Use the code-review skill to review the attached pull request and route the changes to the most relevant specialized review skills based on the languages, frameworks, and concerns present.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I route pull requests to the right technical reviewers?▼

Routing pull requests to the right technical reviewers requires inspecting the diff scope, inferring the primary language and framework from code and metadata, and dispatching to specialized review skills based on detected concerns like over-engineering or component composition.

What is the best way to get relevant code review feedback for multiple frameworks?▼

Getting relevant code review feedback for multiple frameworks involves detecting the specific ecosystems present in your changes, such as Go or React, and automatically applying specialized guidance rather than relying on generic review rules.

Does code review routing work with pasted snippets and selected files?▼

Code review routing works with pasted snippets, selected files, git diffs, PRs, and branches by inspecting the review scope first to infer the primary technology and identify any specific review concerns present.

Can I detect and simplify over-engineered code during a diff analysis?▼

You can detect and simplify over-engineered code during a diff analysis when redundant checks or verbosity are identified as the main concern, which triggers routing to a dedicated simplification skill for cleanup.

When do I need framework detection for reviewing branches?▼

Framework detection for reviewing branches is needed when multiple ecosystems or concerns appear in the changes, requiring automated identification of primary technologies to apply the correct specialized review guidance.