code-review

Review git changes with stack-specific rules and severity-based reporting.

28|3|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/felipereisdev/code-review-skill --skill code-review-felipereisdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/felipereisdev/code-review-skill/tree/main
Command: npx skills add https://github.com/felipereisdev/code-review-skill --skill code-review-felipereisdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews are often inconsistent, miss stack-specific best practices, and lack structured severity classification, leading to missed critical issues and wasted time on minor suggestions. This skill automates comprehensive, tailored code reviews that adapt to your project's technology stack and architectural patterns.

Core Features & Use Cases

  • Automatic Stack Detection: Identifies your project's tech stack from config files and applies only relevant, stack-specific review rules for 19 supported technologies including React, Laravel, Python, and Terraform.
  • Severity-Based Reporting: Classifies all findings as Critical (merge blockers), Warning (should fix soon), or Suggestion (optional improvements) with clear, actionable fix recommendations.
  • Consistency Enforcement: Checks existing project conventions before flagging violations to avoid enforcing arbitrary patterns that don't match your codebase.
  • Use Case: Ideal for development teams wanting consistent, high-quality PR reviews without requiring every reviewer to memorize stack-specific best practices, or for solo developers wanting a second pair of eyes on their changes.

Quick Start

Ask your AI assistant to run the code-review skill to review your recent git changes for issues across security, performance, architecture, and more.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code reviews for pull requests across different tech stacks?

Automated code review tools analyze git changes and apply stack-specific rules to identify issues in pull requests. This skill detects 19 supported technologies like React, Laravel, and Terraform, then reports findings with severity classifications and actionable fix recommendations.

How does stack-aware static analysis reduce false positives in code reviews?

Stack-aware static analysis reduces false positives by validating library API usage against live documentation and enforcing project consistency checks before flagging pattern violations. This ensures the review only applies relevant, stack-specific best practices rather than arbitrary rules.

Can I use automated code review for Clean Architecture, DDD, CQRS, and microservices?

Yes, automated code review can validate Clean Architecture, DDD, CQRS, and microservices patterns. The skill applies architectural pattern guidelines to your git changes and flags violations while checking existing project conventions to ensure consistency.

What is severity-based reporting in code reviews and how does it classify findings?

Severity-based reporting in code reviews classifies findings as Critical merge blockers, Warning items to fix soon, or Suggestion improvements for optional changes. This structured approach prioritizes security, performance, and architecture issues with clear, actionable fix recommendations.

Does the code review skill work without integrating external static analysis dependencies?

Yes, the code review skill operates without external dependencies. It uses built-in stack detection to identify your project's tech stack from config files and applies internal rules for security, performance, and architectural pattern validation.

Why does my static analysis tool flag code that matches my existing project conventions?

Generic static analysis tools often flag code matching existing project conventions because they enforce arbitrary patterns. This skill checks existing project conventions before flagging violations, ensuring pattern enforcement matches your actual codebase.