skills.rest
nguyenthienthanh
nguyenthienthanhCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-reviewer

Automate code review with multi-agent analysis and Markdown reports.

24|3|Updated Nov 25, 2025
Search Tags:#automation#git#developer tools#quality assurance#code review#security audit#performance check
One-click install
npx skills add https://github.com/nguyenthienthanh/aura-frog --skill code-reviewer-nguyenthienthanh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/nguyenthienthanh/aura-frog/tree/main/aura-frog/skills/code-reviewer
Command: npx skills add https://github.com/nguyenthienthanh/aura-frog --skill code-reviewer-nguyenthienthanh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews are time-consuming, inconsistent, and prone to human error, leading to missed bugs, security vulnerabilities, and inconsistent code quality. This Skill automates the comprehensive code review process, ensuring high standards.

Core Features & Use Cases

  • Multi-Agent Analysis: Leverages specialized agents to check for security (OWASP Top 10), development best practices (KISS, error handling), QA (coverage, test quality), and performance (algorithms, memory).
  • Automated Report Generation: Produces a structured code review report with passed checks, warnings, critical issues, and key metrics.
  • Merge Decision Guidance: Provides clear recommendations (Approved, Approved with Comments, Changes Requested) to streamline the merge process.
  • Use Case: Before merging a pull request, invoke this skill to get an automated, multi-faceted report on security, quality, testing, and performance, ensuring the code meets all standards.

Quick Start

Review the latest code changes before merging to main

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 reviews before merging pull requests?▼

Automated code reviews use multi-agent analysis to check security, performance, and maintainability across diffs. This Skill orchestrates specialized agents—covering OWASP vulnerabilities, dev best practices, test quality, and algorithm efficiency—then generates a structured report with merge guidance (Approved, Approved with Comments, or Changes Requested) so reviewers have actionable findings before merging.

What security and quality issues does automated code review catch?▼

Automated review identifies OWASP Top 10 vulnerabilities, error handling gaps, code maintainability problems, test coverage shortfalls, memory leaks, and algorithm inefficiencies. The multi-agent approach applies dev practices (KISS principle), QA standards, and performance analysis across your repository changes to flag critical issues, warnings, and passed checks in one structured report.

Can I use automated code review across different repositories and Git workflows?▼

Yes. This Skill applies to post-implementation and pre-merge codebases across repositories. It extracts diffs from your Git changes, runs security, dev, QA, and performance analysis on those diffs, then outputs a standardized Markdown report with merge recommendations—compatible with any Git-based workflow or repository structure.

What's the difference between manual code review and automated multi-agent review?▼

Manual review is time-consuming, inconsistent, and prone to human error; automated multi-agent review is faster and standardized. This approach applies specialized agents in parallel—each focusing on security, development practices, QA, or performance—so coverage is comprehensive, consistent across reviews, and human reviewers get prioritized findings instead of raw diffs.

How do I generate a code review report with actionable merge decisions?▼

Invoke this Skill on your pull request before merging. It extracts code changes, runs multi-agent analysis (Security, Dev, QA, Performance), and produces a structured Markdown report showing passed checks, warnings, critical issues, key metrics, and a clear merge recommendation—giving you everything needed to decide whether to approve, approve with comments, or request changes.

When should I run automated code review in my development workflow?▼

Run automated code review immediately before merging to main or a release branch. The Skill analyzes post-implementation changes and pre-merge diffs to catch security vulnerabilities, quality gaps, and performance regressions early—preventing bugs and inconsistent standards from reaching production.

Related Skills

Explore More Software Engineering Skills→
StudyDriftStudyDrift
58

make-pr-easy-to-review

Clean noisy PR history and add reviewer guidance without altering code behavior.

Official
Intermediate
addxaiaddxai
42

security-compliance-review

Detects secret leaks, PII exposure, and compliance violations in code, configuration, and documentation.

Official
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

land-and-deploy

Merge pull requests, monitor CI, deploy to production, and verify health with canary checks.

Community
Intermediate
gztcodegztcode

requesting-code-review

Automate code review with static security scanning, quality gates, and an independent reviewer subagent.

Community
Advanced