code-review

Review code diffs and post prioritized inline comments on pull requests.

9|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/llm011/ethan-agent --skill code-review-llm011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/llm011/ethan-agent/tree/main/ethan/defaults/skills/code-review
Command: npx skills add https://github.com/llm011/ethan-agent --skill code-review-llm011

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify bugs, security vulnerabilities, performance issues, and reliability risks in code changes before they are merged, while keeping reviews focused on actionable findings.

Core Features & Use Cases

  • Diff-Focused Analysis: Reviews only the changed code and avoids unrelated repository files, builds, tests, and cloning.
  • Prioritized Findings: Classifies confirmed issues as P0, P1, or P2 and limits inline comments to problems that warrant action.
  • Pull Request Collaboration: Retrieves GitHub pull request diffs with the GitHub CLI and publishes concise, line-specific review comments.
  • Use Case: Give the Skill a pull request link to inspect the changed files, identify concrete defects, and post prioritized inline feedback in the repository's language.

Quick Start

Use the code-review skill to review the provided pull request diff and publish concise inline comments for any confirmed P0 or P1 issues.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a GitHub pull request for bugs and security issues?

To review a GitHub pull request for bugs and security issues, provide the pull request link to the code review skill. It retrieves the diff using the GitHub CLI and posts prioritized inline comments for confirmed defects.

Does code review work with GitLab merge requests and local diffs?

Code review works with GitLab merge requests and local diffs by analyzing the provided diff directly. Publishing inline comments automatically requires the GitHub CLI and appropriate authentication for GitHub workflows.

How are code review findings prioritized for pull requests?

Code review findings are prioritized by classifying confirmed issues as P0, P1, or P2. The skill limits inline comments to problems that warrant action, ensuring focused and prioritized feedback on defects.

Does the code review skill clone the repository or run tests during analysis?

The code review skill does not clone the repository, run tests, or build files. It performs diff-focused analysis by reviewing only the changed code to identify security vulnerabilities and reliability risks efficiently.

What is the best way to detect security vulnerabilities in a code diff?

The best way to detect security vulnerabilities in a code diff is using diff-focused code review. This process isolates changed code to identify concrete defects and performance problems before merge without unrelated repository scanning.

Why do I need the gh CLI for automated pull request code reviews?

You need the gh CLI for automated pull request code reviews to fetch pull request diffs and publish line-specific review comments back to the repository. Appropriate GitHub authentication is required for this workflow.