code-review

Generate actionable review comments from code quality, security, and performance perspectives.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Holy-Pigeon/AIWorkflow --skill code-review-holy-pigeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Holy-Pigeon/AIWorkflow/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/Holy-Pigeon/AIWorkflow --skill code-review-holy-pigeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze PR diffs and generate review comments from code quality, security, and performance perspectives. Use for code reviews, quality checks, and security analysis.

Core Features & Use Cases

  • Generate actionable review comments with filename, line number, issue description, and severity.
  • Assess code quality, security, and performance across PR changes to surface risks and improvement opportunities.
  • Use Case: Integrate into CI/CD to automatically annotate PRs with structured feedback.

Quick Start

Review the latest PR diff and return a structured set of line-specific review comments.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automatically analyze PR diffs for code quality and security issues?

To analyze PR diffs, this Skill reviews file paths and changes to identify code quality, security, and performance issues, returning structured comments with filenames, line numbers, and severity levels.

What is the best way to generate actionable line-specific comments for a pull request review?

Generating actionable PR review comments requires heuristic analysis and lightweight static checks on the diff, which produces prioritized feedback detailing exact line numbers and issue descriptions.

Can I use heuristic analysis to surface performance risks in code changes?

Yes, you can use heuristic analysis to assess performance risks across code changes, evaluating the PR diff to surface improvement opportunities and generate structured performance feedback.

Does this code review approach work for integrating automated annotations into a CI/CD pipeline?

Yes, this code review approach works for CI/CD pipelines by taking PR diffs as input to automatically annotate pull requests with structured, actionable quality and security feedback.

What are the limitations of using lightweight static checks for security audits?

Lightweight static checks for security audits rely on heuristic analysis of file paths and diffs, meaning they surface risks and improvement opportunities but may not catch deep runtime vulnerabilities.