code-review

Analyze code diffs for bugs, style, performance, and security issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers improve the quality of their code by systematically reviewing it for bugs, style inconsistencies, performance issues, and security vulnerabilities.

Core Features & Use Cases

  • Comprehensive Code Analysis: Checks for logic errors, adherence to project conventions, performance bottlenecks, and security risks.
  • Language-Specific Checks: Includes tailored checks for Rust and TypeScript.
  • Structured Feedback: Provides clear, actionable feedback using specific markers (🐛 Bug, 💡 Suggestion, ⚠️ Warning, ✅ Looks good).
  • Use Case: Before merging a new feature branch, use this Skill to get a detailed review of the changes, ensuring they meet quality standards and are free of common pitfalls.

Quick Start

Review the code changes in the current branch for bugs and style issues.

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 for bugs and security vulnerabilities before merging?

Review code changes for bugs and security vulnerabilities by analyzing diffs from pull requests, branches, or staged changes. The review identifies logic errors, performance bottlenecks, and security risks to enforce best practices and improve code quality before merging.

Does code review work with TypeScript and Rust?

Yes, code review works with TypeScript and Rust. The analysis includes tailored language-specific checks for both, ensuring adherence to project conventions and catching common pitfalls unique to each language.

What is the best way to check a feature branch for style inconsistencies?

The best way to check a feature branch for style inconsistencies is to analyze the branch diff systematically. The review enforces project conventions and provides structured feedback using markers like 💡 Suggestion and ⚠️ Warning to highlight style issues.

How do I get actionable feedback on my pull request diff?

Get actionable feedback on your pull request diff through structured output. The review provides clear markers like 🐛 Bug, 💡 Suggestion, ⚠️ Warning, and ✅ Looks good to categorize logic errors, performance issues, and style adherence.

Can I analyze staged files for performance bottlenecks before committing?

Yes, you can analyze staged files for performance bottlenecks before committing. The review process accepts staged changes as input and identifies performance bottlenecks alongside logic errors and security vulnerabilities.

What types of code issues can a code review catch?

A code review can catch logic errors, performance bottlenecks, security vulnerabilities, and style inconsistencies. It systematically analyzes code changes to ensure they meet quality standards and are free of common pitfalls before integration.