code-review

Automate code review to detect style issues, linting violations, and potential bugs.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/gongye19/manu-agno --skill code-review-gongye19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/gongye19/manu-agno/tree/main/cookbook/02_agents/16_skills/sample_skills/code-review
Command: npx skills add https://github.com/gongye19/manu-agno --skill code-review-gongye19

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Code review can be time-consuming; this Skill automates detection of style inconsistencies, linting violations, and potential bugs to improve code quality.

Core Features & Use Cases

  • Automated Style Checks: Enforces project-specific style rules and known best practices.
  • Issue Detection: Highlights potential bugs, anti-patterns, and security concerns during review.
  • Use Case: During a pull request, run automated checks to surface style issues and suggested fixes before merging.

Quick Start

Submit the code snippet to be reviewed and receive linting results with suggested fixes.

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 review to detect linting violations and style issues?

Automated code review detects style inconsistencies, linting violations, and potential bugs by running static analysis tooling with defined style-guide references to generate actionable feedback during pull request validation.

Can I run automated style checks during a pull request before merging?

Yes, automated style checks run during pull requests to enforce project-specific style rules and surface known best practice violations with suggested fixes before pre-merge validation.

What static analysis tools do I need for automated code review?

Automated code review requires static analysis tooling, a defined style-guide reference, and optional rules in scripts to perform checks and generate actionable feedback on codebases.

Does automated code review work for large codebases in CI pipelines?

Yes, automated code review is useful for small to large codebases during CI pipelines, detecting anti-patterns, security concerns, and style inconsistencies to improve overall code quality.

How do I enforce project-specific style rules and best practices automatically?

You enforce project-specific style rules by configuring static analysis tooling with a defined style-guide reference and optional script rules to highlight anti-patterns and suggest fixes.

What is the best way to surface potential bugs and security concerns during code review?

Automated code review surfaces potential bugs and security concerns by running static analysis checks that highlight anti-patterns and style violations, generating actionable feedback with suggested fixes.