pre-pr

Analyze git diffs and run targeted review checklists to produce a GO/NO-GO report.

6|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/wesleyosantos91/multi-agents --skill pre-pr-wesleyosantos91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-pr
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/pre-pr
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill pre-pr-wesleyosantos91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of submitting a pull request without catching correctness, security, testing, contract, or dependency issues early.

Core Features & Use Cases

  • Diff-first review: derives the full change set by analyzing git diff main...HEAD to understand modified, added, and removed files.
  • Domain checklist orchestration: runs targeted reviews by invoking roles like tech-lead-reviewer, security-reviewer, qa-quality-engineer, api-contract-reviewer, and dependency-versions-reviewer as needed.
  • Pre-flight validation: verifies tests pass, checks for secrets in files like .env/credentials/tokens, and ensures no pending TODOs/FIXMEs remain in the changes.
  • Decision-ready reporting: produces a structured GO/NO-GO report with justification per checklist item.

Quick Start

Use the pre-pr skill to run a complete pre-PR checklist and return a GO/NO-GO report with itemized justifications for the current branch changes.

Frequently Asked Questions about pre-pr

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

FAQPage Schema
How do I run a pre-PR code review and validation on my feature branch?

Pre-PR validation works by deriving the full git diff change set and running targeted review checklists for engineering, security, QA, API contracts, and dependencies before opening a pull request.

What is included in a pre-pull-request validation checklist?

A pre-pull-request validation checklist includes diff analysis, tech lead review, security checks for exposed secrets, QA test verification, API contract validation, and dependency version checks to ensure branch readiness.

How do I check for exposed secrets and pending TODOs before opening a pull request?

Pre-PR validation checks for exposed secrets and pending TODOs by scanning file changes and credential files during the pre-flight stage to ensure no sensitive data or incomplete tasks reach the main branch.

Does pre-PR validation work for refactoring branches and API contract changes?

Yes, pre-PR validation works for refactoring branches and API contract changes by applying targeted review checklists to verify correctness, test health, and compatibility before code is officially reviewed.

How do I get a structured GO or NO-GO decision report for my git diff?

You get a structured GO or NO-GO decision report by running domain checklist orchestration on your git diff, which evaluates security, QA, and dependencies, returning a decision report with per-item rationale.

What is the best way to verify test health and dependency versions before a pull request?

The best way to verify test health and dependency versions is running a pre-PR validation that orchestrates QA and dependency reviewers on your change set to catch compatibility issues early.