github-code-review

Reviews local git diffs and GitHub PR diffs for bugs, security issues, and missing tests.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/raulisai/eva02 --skill github-code-review-raulisai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/raulisai/eva02/tree/main/apps/eva-core/src/skills/github/github-code-review
Command: npx skills add https://github.com/raulisai/eva02 --skill github-code-review-raulisai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing code changes manually is slow and error-prone, especially when checking for security flaws, tenant isolation regressions, and missing test coverage across large diffs. This Skill automates structured code review of local git changes or GitHub pull request diffs, producing severity-ranked findings with file and line references. ## Core Features & Use Cases - Diff-Based Review: Inspects local changes via git diff, staged changes, commit ranges, or GitHub PR diffs via the gh CLI. - EVA-Specific Checks: Verifies org_id tenant filtering, RLS migration updates, secret handling, Approval Engine usage, and state machine compliance. - Severity-Ranked Output: Reports findings first with [P0]/[P1]/[P2] labels, using a structured template covering critical issues, warnings, suggestions, and positive observations. - Use Case: Before pushing a feature branch, ask for a review of your staged changes to catch a missing org_id filter on a new tenant-data query before it reaches production. ## Quick Start Review my staged git changes for security issues, tenant isolation problems, and missing tests, then report findings ordered by severity.

Frequently Asked Questions about github-code-review

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

FAQPage Schema
How do I review a GitHub pull request diff automatically?

Use the gh pr diff command to inspect a pull request diff when GitHub access is already configured. The review checks security, error handling, tests, and backward compatibility, then reports findings ordered by severity with file and line references.

How to review local git changes before pushing?

Run the review against git diff, git diff --staged, or a commit range such as main...HEAD. Findings are presented as a severity-structured message covering critical issues, warnings, and suggestions without posting anything to GitHub.

What security checks does an automated code review cover?

The review verifies that tenant-data queries filter by org_id, new tables include migrations and RLS policy updates, secrets are not committed or exposed to client code, and destructive actions route through an approval engine.

Can the review post comments or approve PRs on GitHub?

Not by default. The skill operates read-only, and posting comments, approving PRs, pushing, merging, or using GitHub credentials requires explicit user approval under the EVA Runtime Skill Policy.

What happens if GitHub authentication is not configured?

The review falls back to local diffs instead of scraping tokens from dotfiles or credential stores. You can provide a safe configured authentication path or simply review local changes with git diff.