auto-code-review

Analyze changed files and generate severity-ranked code review feedback.

11|1|Updated Jan 5, 2015
One-click install
npx skills add https://github.com/ryonakae/dotfiles --skill auto-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-code-review
Source: https://github.com/ryonakae/dotfiles/tree/main/config/.agents/skills/auto-code-review
Command: npx skills add https://github.com/ryonakae/dotfiles --skill auto-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates code reviews based on SOLID, DRY, KISS and language-specific best practices to provide structured feedback on changes, reducing manual review effort and improving code quality.

Core Features & Use Cases

  • Analyzes modified files to identify violations of SOLID, DRY, and KISS principles.
  • Generates severity-ranked feedback with concrete improvement suggestions and rationale.
  • Supports PR or pre-commit workflows by producing actionable reports on demand.

Quick Start

Analyze the latest commit or pull request and return a prioritized code-review report.

Frequently Asked Questions about auto-code-review

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

FAQPage Schema
How do I automate code reviews for SOLID, DRY, and KISS violations?

You can automate code reviews by analyzing modified files to detect violations of SOLID, DRY, and KISS principles. This process generates severity-ranked feedback with concrete improvement suggestions and rationale, producing actionable reports on demand.

What is static analysis for code quality and how does it classify findings?

Static analysis for code quality evaluates changed files against language-specific best practices. It classifies identified issues by severity and returns concrete remediation suggestions suitable for both automated and human review workflows.

Can I use automated code review for pull request and pre-commit workflows?

Yes, automated code review supports pull request and pre-commit workflows by producing actionable reports on demand. It analyzes changed files during feature completion or when asked to review code and check implementation.

What's the best way to check implementation quality before completing a feature?

The best way to check implementation quality is to apply static analysis during feature completion. This evaluates modified files against established software engineering principles and returns prioritized, concrete remediation suggestions to improve code consistency.

Does automated static analysis provide rationale for code review suggestions?

Yes, automated static analysis provides rationale for its code review suggestions. It generates severity-ranked feedback that includes concrete improvement suggestions and the reasoning behind each identified violation of software engineering principles.