code-reviewer

Review git diffs and pull requests for merge risks with evidence-based findings.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill code-reviewer-nguyenpv1980-wq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/code-reviewer
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill code-reviewer-nguyenpv1980-wq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill reviews actual code changes before merge so maintainers can catch correctness, security, reliability, and test coverage issues with evidence instead of guesswork.

Core Features & Use Cases

  • Diff-Based Review: Evaluates a real PR, branch, commit, or staged diff and refuses to review imagined code.
  • Severity-Ranked Findings: Reports blocker, major, minor, and nit issues with file:line anchors, failure scenarios, and concrete remediation.
  • Context-Aware Analysis: Reads surrounding unchanged code, tests, migrations, and config to judge the change in context.
  • Use Case: A developer opens a pull request that adds a new endpoint and migration, and this Skill identifies auth, rollback, and test gaps before merge.

Quick Start

Ask the code-reviewer skill to review the actual diff for my branch and return severity-ranked findings with file-line evidence and a merge verdict.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review a git diff for merge risks before opening a pull request?

Review a pull request diff by analyzing correctness, security, reliability, and test coverage issues with evidence-based findings ranked by severity, complete with file:line anchors and concrete remediation steps.

What is evidence-based code review and how does it work with actual diffs?

Evidence-based code review evaluates an actual git diff or pull request by reading surrounding unchanged code, tests, and migrations to report context-aware findings with file:line evidence and a merge verdict instead of guesswork.

How do I get severity-ranked findings for my pull request changes?

Get severity-ranked findings for pull request changes by submitting the actual diff, which is evaluated to report blocker, major, minor, and nit issues with file:line anchors, failure scenarios, and concrete remediation steps.

Can I use automated code review for database migrations and security checks?

Automated code review for database migrations and security checks applies to actual change sets by reading migration files and surrounding context to identify auth gaps, rollback issues, and test coverage problems before merge.

Does diff analysis work without access to the full repository context?

Diff analysis requires real diff access and surrounding code context, explicitly refusing to review imagined code to ensure actionable verdicts based on unchanged code, tests, migrations, and config.

When should I not use automated diff analysis for code review?

Avoid automated diff analysis when you lack real diff access or surrounding code context, as the review requires actual git changes, tests, and config to produce evidence-based findings and a reliable merge verdict.