code-reviewer

Automates code review across Rust, Python, JavaScript, and Go for pull requests and CI pipelines.

19|3|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/louloulin/claude-agent-sdk --skill code-reviewer-louloulin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/louloulin/claude-agent-sdk/tree/main/crates/claude-agent-sdk/examples/.claude/skills/code-reviewer
Command: npx skills add https://github.com/louloulin/claude-agent-sdk --skill code-reviewer-louloulin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires linter, security-analyzer.

What problem does it solve?

This Skill automates thorough code reviews to identify quality gaps, security risks, and performance issues early in the development cycle.

Core Features & Use Cases

  • Automated quality checks: leverages linter rules to detect code smells, anti-patterns, and style violations.
  • Security and performance feedback: highlights vulnerabilities, insecure patterns, and bottlenecks with concrete remediation suggestions.
  • Use Case: In a pull request or CI workflow, run a fast, automated review to surface actionable improvements before merging.

Quick Start

Use the code-reviewer skill to scan the latest PR diff and generate a prioritized report.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automate code review for security vulnerabilities and code quality in pull requests?

Automate code review by applying linter rules to detect code smells and security vulnerabilities in pull requests. This process surfaces actionable improvements and provides recommended fixes before merging, enforcing maintainability and security standards.

Can I run automated security analysis and linting in CI pipelines across multiple programming languages?

Yes, automated security analysis and linting can run in CI pipelines across Rust, Python, JavaScript, and Go. It highlights insecure patterns and bottlenecks, generating a prioritized report with concrete remediation suggestions during the development cycle.

What is the best way to detect performance bottlenecks and anti-patterns before merging code?

The best way to detect performance bottlenecks and anti-patterns is using an automated code review tool that leverages linter rules. It identifies style violations and security risks early, providing prioritized, actionable feedback for developers before merging.

Does automated code review work with linter and security-analyzer dependencies?

Yes, automated code review works directly with linter and security-analyzer dependencies. It leverages these components to enforce testing standards, detect anti-patterns, and highlight vulnerabilities across supported programming languages in pull requests.