code-review-ai-ai-review
Makes your agent review code like an expert, using AI tools. It combines automated analysis and pattern recognition to ensure quality.
What it does
This tool helps review your programming code. It looks for errors, security issues, and suggests improvements to make your code better and safer.
When to use it
- ✓When you finish writing a piece of code.
- ✓Before sharing your code with others.
- ✓When you want to ensure your code is secure and efficient.
Example of what to ask your AI
“Review this Python code for bugs and security vulnerabilities.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool uses other AI and analysis tools to examine your code. It checks for known error patterns and security issues, and also uses artificial intelligence to understand your code's context and find more subtle problems.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill code-review-ai-ai-reviewOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/code-review-ai-ai-review/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Supporting material availability
This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files:
<support-root>/scripts/ai_review.py
Ask for the original supporting material or an existing installation before using a step that depends on these paths; this catalog does not identify a verified download source for them. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable.
AI-Powered Code Review Specialist
You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, Claude 4.5 Sonnet) with battle-tested platforms (SonarQube, CodeQL, Semgrep) to identify bugs, vulnerabilities, and performance issues.
Use this skill when
- Working on ai-powered code review specialist tasks or workflows
- Needing guidance, best practices, or checklists for ai-powered code review specialist
Do not use this skill when
- The task is unrelated to ai-powered code review specialist
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
Context
Multi-layered code review workflows integrating with CI/CD pipelines, providing instant feedback on pull requests with human oversight for architectural decisions. Reviews across 30+ languages combine rule-based analysis with AI-assisted contextual understanding.
Requirements
Review: $ARGUMENTS
Perform comprehensive analysis: security, performance, architecture, maintainability, testing, and AI/ML-specific concerns. Generate review comments with line references, code examples, and actionable recommendations.
Automated Code Review Workflow
Initial Triage
- Parse diff to determine modified files and affected components
- Match file types to optimal static analysis tools
- Scale analysis based on PR size (superficial >1000 lines, deep <200 lines)
- Classify change type: feature, bug fix, refactoring, or breaking change
Multi-Tool Static Analysis
Execute in parallel:
- CodeQL: Deep vulnerability analysis (SQL injection, XSS, auth bypasses)
- SonarQube: Code smells, complexity, duplication, maintainability
- Semgrep: Organization-specific rules and security policies
- Snyk/Dependabot: Supply chain security
- GitGuardian/TruffleHog: Secret detection
AI-Assisted Review
# Context-aware review prompt for Claude 4.5 Sonnet
review_prompt = f"""
You are reviewing a pull request for a {language} {project_type} application.
**Change Summary:** {pr_description}
**Modified Code:** {code_diff}
**Static Analysis:** {sonarqube_issues}, {codeql_alerts}
**Architecture:** {system_architecture_summary}
Focus on:
1. Security vulnerabilities missed by static tools
2. Performance implications at scale
3. Edge cases and error handling gaps
4. API contract compatibility
5. Testability and missing coverage
6. Architectural alignment
For each issue:
- Specify file path and line numbers
- Classify severity: CRITICAL/HIGH/MEDIUM/LOW
- Explain problem (1-2 sentences)
- Provide concrete fix example
- Link relevant documentation
Format as JSON array.
"""
Model Selection (2025)
- Fast reviews (<200 lines): GPT-4o-mini or Claude 4.5 Haiku
- Deep reasoning: Claude 4.5 Sonnet or GPT-5 (200K+ tokens)
- Code generation: GitHub Copilot or Qodo
- Multi-language: Qodo or CodeAnt AI (30+ languages)
Review Routing
interface ReviewRoutingStrategy {
async routeReview(pr: PullRequest): Promise<ReviewEngine> {
const metrics = await this.analyzePRComplexity(pr);
if (metrics.filesChanged > 50 || metrics.linesChanged > 1000) {
return new HumanReviewRequired("Too large for automation");
}
if (metrics.securitySensitive || metrics.affectsAuth) {
return new AIEngine("claude-3.7-sonnet", {
…
FAQ
What is 'static analysis'?
It's like a proofreader that reads your code without running it, looking for syntax errors, potential bugs, and violations of programming rules.
What kinds of problems does it find?
It can find common bugs, security vulnerabilities (like flaws that allow hacking), performance issues, and suggestions to make the code easier to understand and maintain.
Does it replace a human reviewer?
Not entirely. It's a great assistant for finding common and repetitive issues, but complex decisions about architecture or business logic still require a human.
Details
Original description by the author
You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C
Popularity
- GitHub stars
- 48k
- Ranking position
- #2572
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
benchmark-optimization-loop
Has your agent improve something's speed in a measured way. It tests multiple versions and chooses the fastest one that still works correctly.
affaan-m/ECC
change-impact
Helps your agent analyze the impact of code changes before making them. It compares the planned vs. actual results afterward, covering paths, data, tests, and documentation. Useful for risky or system-wide changes.
affaan-m/ECC
click-path-audit
Lets your agent trace all user buttons and interactions to find bugs. It finds issues where functions seem to work alone but fail together. Useful when bugs persist even after debugging.
affaan-m/ECC