code-review-assistant

Analyze code diffs to identify bugs, style violations, and logic errors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the detection of bugs, style violations, and logical errors during code reviews to improve quality and consistency.

Core Features & Use Cases

  • Code Review Assistant: Automates the routine checks for bugs, style, and logic.
  • Refactoring Suggester: Proposes safer, clearer improvements to junior-level code.
  • Documentation Generator: Produces rationale and comments to accompany changes.

Quick Start

Run the skill against the diff from your pull request to generate a set of review comments and suggested fixes.

Frequently Asked Questions about code-review-assistant

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

FAQPage Schema
How do I automate code review for a pull request diff?

Automated code review processes a pull request diff to identify bugs, style violations, and logic errors, generating file-level comments and actionable suggestions. You can run this analysis locally against your code changes.

Can static analysis detect dead code and style violations across varied codebases?

Static analysis can detect dead code and style violations across varied codebases by aligning with editorconfig and lint rules. It analyzes code diffs locally to pinpoint logic errors and provide actionable improvements.

Does this automated code review work with any programming language?

Automated code review applies to pull requests across varied languages and codebases. It processes code diffs locally to detect bugs and align with lint rules without requiring language-specific setup.

How do I generate rationale and comments for code refactoring suggestions?

Generating rationale for code refactoring involves analyzing code diffs to propose safer, clearer improvements to junior-level code. It produces documentation and comments to accompany the suggested changes.

What is the best way to detect logic errors in a code diff locally?

The best way to detect logic errors locally is to run static analysis on the code diff. This identifies bugs, style violations, and dead code, providing file-level review comments and actionable suggestions.

What are the limitations of automated static analysis for code review?

Limitations of automated static analysis include its reliance on processing code diffs locally, meaning it focuses on file-level review comments and may not catch complex runtime bugs or architectural issues outside the diff context.