code-review

Analyze git diffs and files for bugs, vulnerabilities, and style issues.

186|10|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/initializ/forge --skill code-review-initializ
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/code-review
Command: npx skills add https://github.com/initializ/forge --skill code-review-initializ

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, git, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, identifying potential bugs, security vulnerabilities, and style violations, thereby improving code quality and reducing manual review time.

Core Features & Use Cases

  • Diff Review: Analyzes code differences between branches or commits.
  • File Review: Performs a deep analysis of individual files for comprehensive assessment.
  • Security Audits: Focuses on identifying security-related issues.
  • Use Case: When submitting a pull request, use this Skill to get an immediate AI-driven review of your changes against the main branch, highlighting critical issues before human review.

Quick Start

Use the code-review skill to review my local changes against the main branch in the current directory.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform an AI code review on a local git diff?

Yes, you can review GitHub pull requests by using this Skill to analyze the code differences. It performs an AI-driven review highlighting critical issues and security vulnerabilities before human review.

Can I use this to run a security audit on my code changes?

To perform a comprehensive assessment, use the file review feature to perform a deep analysis of individual files. This goes beyond simple diffs to evaluate the entire file for bugs and style violations.

Do I need git and LLM API keys to review code?

Yes, you need git and LLM API keys to review code using this Skill. Git is required for operation to process differences, while the API keys power the underlying AI-driven analysis of your codebase.

What is the best way to identify bugs in a pull request automatically?

This Skill is limited to analyzing code differences and individual files for bugs, security vulnerabilities, and style issues. It requires git and LLM API keys, and does not execute or compile your code.