code-review

Name: code-review
Availability: InStock
Author: eric-sabe

Review local Git diffs for code quality, security, and functional defects.

1|Updated Jun 24, 2026

Search Tags:#code quality #git #code review #pull request #security #pre-push #ci

Ready to run

npx skills add https://github.com/eric-sabe/engsys --skill code-review-eric-sabe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/eric-sabe/engsys/tree/main/core/skills/code-review
Command: npx skills add https://github.com/eric-sabe/engsys --skill code-review-eric-sabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the inefficiency of post-push code review loops that waste CI minutes and delay PR merges by enabling thorough local review of code changes before they are pushed to the remote repository.

Core Features & Use Cases

Default Pre-Push Review: Built-in skill that triggers automatically when the agent detects a need for review of code, PRs, quality, or security changes, or on explicit user request.
Severity Triage: Categorizes review findings by Critical, Warning, and Info severity to prioritize fixes for high-impact issues first.
PR Integration: Persists local review findings as PR comments to streamline the closeout process and avoid redundant review work.
Use Case: Run this skill before pushing any feature branch changes to catch bugs, security flaws, or quality issues early, so your PR opens already reviewed and passes CI on the first run.

Quick Start

Run the built-in /code-review skill against the current branch's diff from origin/main before pushing any code changes to catch and fix issues early.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I run a local pre-push code review to catch security and quality issues before pushing my Git branch?▼

Run a local pre-push code review against your branch diff from origin/main to identify code quality, security, and functional defects before changes are pushed to the remote repository.

Can I persist local code review findings as PR comments to streamline the pull request closeout process?▼

Yes, local code review findings can be persisted as PR comments to streamline the closeout process and avoid redundant review work on the pull request.

How does pre-push code review help save CI minutes and avoid post-push review loops?▼

Pre-push code review catches bugs and security flaws locally before changes are pushed, eliminating post-push CI review loops that waste CI minutes and delay PR merges.

What severity levels are used to triage code quality and security defects found during a pre-push review?▼

Pre-push review findings are categorized by Critical, Warning, and Info severity to prioritize fixes for high-impact code quality and security issues first.

When should I trigger a pre-push code review for my feature branch changes?▼

Trigger a pre-push code review explicitly by user request or when the agent detects a need for review of code, PRs, quality, or security changes before pushing any feature branch.

Do I need any external dependencies or CI tools to perform a local Git pre-push code review?▼

No external dependencies or CI tools are required; the pre-push code review runs locally against your Git diff to catch issues before pushing to the remote repository.