prereview

Analyze unpushed commits for bugs, security issues, and error handling gaps.

5|5|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/erraggy/oastools --skill prereview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prereview
Source: https://github.com/erraggy/oastools/tree/main/.claude/skills/prereview
Command: npx skills add https://github.com/erraggy/oastools --skill prereview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines pre-push code reviews by automatically analyzing unpushed changes for bugs, security issues, and error handling gaps before they reach a shared repository.

Core Features & Use Cases

  • Identifies unpushed changes on the current branch and checks for potential regressions before pushing.
  • Runs multiple review agents in parallel (code-reviewer, silent-failure-hunter, code-simplifier, comment-analyzer, pr-test-analyzer, type-design-analyzer) to surface issues and provide remediation guidance.
  • Use case: when preparing to push, run the prereview skill to validate changes and generate a consolidated findings summary for the team.

Quick Start

Run prereview on your current branch to perform a comprehensive pre-push analysis and generate a prioritized findings report.

Frequently Asked Questions about prereview

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

FAQPage Schema
How do I automate pre-push code review for unpushed git commits?

Automating pre-push code review involves analyzing unpushed commits on your current branch to catch bugs and security issues before they reach the remote repository. This skill aggregates diffs and coordinates multiple review agents to produce a unified assessment.

What is the best way to catch security issues before pushing code?

The best way to catch security issues before pushing is to run automated pre-push checks that inspect unpushed diffs. By coordinating multiple review agents, you can surface vulnerabilities and error handling gaps locally before they affect the shared repository.

How does pre-push analysis detect error handling gaps in my code?

Pre-push analysis detects error handling gaps by inspecting aggregated diffs from unpushed commits and applying specialized review agents. These agents parse the changes, run checks, and summarize findings to provide remediation guidance before the push occurs.

Can I run multiple code review agents in parallel before pushing to remote?

Yes, you can run multiple code review agents in parallel before pushing to remote. This skill coordinates agents like silent-failure-hunter and code-simplifier to analyze unpushed changes simultaneously and generate a consolidated findings summary.

Does automated pre-push code review preserve local git changes?

Automated pre-push code review preserves local git changes by running safe guardrails during diff parsing and analysis. The process only inspects unpushed commits to generate findings without modifying your local codebase.

What types of code issues can a pre-push review agent identify?

A pre-push review agent can identify bugs, security vulnerabilities, type design flaws, and silent failures. By analyzing unpushed diffs, agents also provide comment analysis and code simplification recommendations before changes reach the remote repository.