skills.rest
ezjonline
ezjonlineCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agent-review

Review changed code files for correctness, edge cases, and security.

1|Updated Apr 10, 2026
Search Tags:#quality assurance#code review#security audit#refactor#bug detection#peer review
One-click install
npx skills add https://github.com/ezjonline/ezj-automations --skill agent-review-ezjonline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-review
Source: https://github.com/ezjonline/ezj-automations/tree/main/skills/agent-review
Command: npx skills add https://github.com/ezjonline/ezj-automations --skill agent-review-ezjonline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the risk of shipping bugs, regressions, and unnecessary complexity by adding a structured second-pass review after implementation work.

Core Features & Use Cases

  • Fresh-eyes review: Spawns a reviewer agent that inspects changed files without sunk-cost bias.
  • Quality checks: Evaluates correctness, edge cases, simplification opportunities, and security concerns.
  • Repair loop: Uses review findings to apply direct fixes and verify the updated files again.
  • Use case: After a feature branch or refactor, it helps confirm the implementation is sound before you hand it off or merge it.

Quick Start

Ask the agent-review skill to review the files you just changed and apply any clearly correct fixes it finds.

Frequently Asked Questions about agent-review

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

FAQPage Schema
How do I run an automated code review on my recent feature changes?▼

To perform a security audit and bug detection on changed files, a fresh reviewer agent reads the modified code, identifies line-level vulnerabilities and edge cases, and applies direct fixes to resolve confirmed findings.

What is the best way to catch bugs and security issues before merging a feature branch?▼

To catch bugs before merging, a structured second-pass review evaluates implemented code changes for correctness, simplification opportunities, and security concerns without sunk-cost bias.

Can I use this peer review process to apply fixes automatically after a refactor?▼

Yes, after a refactor, this peer review process uses a repair loop to apply clearly correct fixes and verify the updated files again before completion.

When do I need a second-pass code review for my implementation?▼

You need a second-pass code review after non-trivial implementations, refactors, and feature work when a fresh-eyes audit is required to confirm the implementation is sound before handoff or merge.

Does this code review approach work without configuring external dependencies?▼

Yes, this code review approach works without external dependencies because it spawns an internal reviewer agent to read modified files and report line-level issues directly.

Why should I use an agent-based reviewer instead of a manual peer review for bug detection?▼

An agent-based reviewer provides a fresh-eyes audit without sunk-cost bias, reading modified files to report line-level issues with concrete fixes, ensuring confirmed findings are resolved before completion.

Related Skills

Explore More Software Engineering Skills→
jrajasekerajrajasekera
1

codex-review

Review design docs and implementation plans to surface issues before implementation.

Community
Intermediate
spencerpaulyspencerpauly
672

grinding-until-pass

Iteratively fix failing tests, builds, and lint checks until they pass.

Community
Advanced
IndustrialIndustrial

code-reviewer

Analyze code for security vulnerabilities and performance issues.

Community
Advanced
shogoggshogogg
4

coderabbit-review

Automate CodeRabbit code reviews for uncommitted and committed Git changes.

Community
Advanced