Pr Preflight

<div> <h1>PR Pre-Flight — Production Risk &amp; Security Review</h1> <p><strong>Catch risky pull requests before they reach production.</strong></p> <p> PR Pre-Flight is an AI-powered pre-merge review skill designed to identify the problems that ordinary linters, CI checks, and generic AI code reviews can miss. </p> <p> Instead of focusing primarily on formatting and stylistic suggestions, PR Pre-Flight examines your <strong>git diff</strong> for production-impacting risks — including breaking API changes, security-sensitive modifications, dependency risks, missing test coverage, and framework-specific hazards. </p> <hr> <h2>🚦 Know the Risk Before You Merge</h2> <p> A pull request can pass tests and still introduce a serious production problem. </p> <p> A required API parameter can break existing clients. A removed permission check can create an authorization vulnerability. A new unpinned dependency can introduce supply-chain risk. A bug fix without a regression test can come back later. </p> <p> <strong>PR Pre-Flight is built to look for exactly these kinds of risks.</strong> </p> <h2>🔍 What It Reviews</h2> <ul> <li> <strong>Breaking API Changes</strong><br> Detects altered function signatures, renamed symbols, changed return types, newly required parameters, and other changes that can break existing callers. </li> ``` <li> <strong>Security-Sensitive Changes</strong><br> Flags potentially dangerous modifications involving authentication, authorization, permissions, secrets, raw SQL, unsafe deserialization, and other security-sensitive code paths. </li> <li> <strong>Dependency &amp; Supply-Chain Risk</strong><br> Reviews dependency changes for new third-party packages, major version upgrades, and unpinned requirements that may increase maintenance or supply-chain risk. </li> <li> <strong>Test Coverage Gaps</strong><br> Cross-checks changed production logic against test changes to identify important code paths that may lack corresponding regression coverage. </li> <li> <strong>Django &amp; FastAPI Deep Review</strong><br> Applies framework-aware checks to migrations, serializers, Pydantic schemas, dependency injection, permissions, and API behavior. </li> ``` </ul> <h2>🧠 More Than a Generic AI Code Review</h2> <p> Generic AI code reviews often produce long lists of style suggestions, minor refactoring ideas, and generic best practices. </p> <p> PR Pre-Flight takes a different approach: it uses a structured review methodology focused on <strong>changes that can create real production risk</strong>. </p> <p> The goal isn't to generate more comments. The goal is to surface the <strong>important risks before the merge button is pressed.</strong> </p> <h2>⚡ Typical Pre-Merge Questions</h2> <p>Use PR Pre-Flight when you want your coding agent to answer questions like:</p> <ul> <li>Could this PR break an existing public API?</li> <li>Did this change accidentally weaken authentication or authorization?</li> <li>Did we introduce a risky dependency?</li> <li>Are important production changes missing tests?</li> <li>Could this Django migration cause deployment or data problems?</li> <li>Did this FastAPI change create a permission or validation issue?</li> <li>What should I fix before merging this PR?</li> </ul> <h2>🛠️ Built for Python Teams</h2> <p>PR Pre-Flight is particularly useful for projects using:</p> <ul> <li>Python</li> <li>Django</li> <li>Django REST Framework</li> <li>FastAPI</li> <li>Pydantic</li> <li>Poetry</li> <li>Pipenv</li> <li>requirements.txt</li> </ul> <h2>🤖 Works With Your AI Coding Agent</h2> <p> Use the skill with the AI development tools you already work with, including Claude Code, Cursor, Codex CLI, GitHub Copilot, Gemini CLI, and other compatible coding agents. </p> <p> The skill is designed to provide a reusable review process rather than requiring you to recreate a complicated prompt every time you review a PR. </p> <h2>📋 Example Review</h2> <p> Imagine a pull request changes a Django API endpoint and removes an existing permission configuration. </p> <p>PR Pre-Flight can surface findings such as:</p> <div> <p><strong>Breaking Change</strong></p> <p> A public API now requires a new parameter that existing callers may not provide. </p> ``` <p><strong>Security Risk</strong></p> <p> A permission check was removed from an authenticated endpoint. </p> ``` </div> <p> This gives the developer a focused risk report before the change is merged. </p> <h2>🎯 Best Use Cases</h2> <ul> <li>Pre-merge PR reviews</li> <li>AI-generated code review</li> <li>Security-focused pull request audits</li>