pr-preflight

Audits changed files, diffs, and stack tooling before opening a pull request.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/arndvs/ctrlshft --skill pr-preflight-arndvs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-preflight
Source: https://github.com/arndvs/ctrlshft/tree/main/skills/pr-preflight
Command: npx skills add https://github.com/arndvs/ctrlshft --skill pr-preflight-arndvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Iterative code review cycles waste time because automated reviewers and human reviewers find issues one at a time across multiple rounds. This Skill front-runs that process by catching the same classes of issues locally before a PR is ever opened or updated. ## Core Features & Use Cases - Diff-Aware Full-File Audit: Resolves the authoritative base branch, maps every changed file, then reads each file completely (not just the diff) to catch security gaps, logic errors, dead code, and inconsistencies. - Stack-Adaptive Tool Checks: Detects TypeScript, Node, Bash, and Python stacks and runs the right validators (tsc, ESLint, tests, ShellCheck, Ruff, Mypy), treating every tool failure as blocking. - Reviewer Simulation & Pre-Push Checklist: Asks the exact questions a reviewer would ask, scans for leftover debug statements and staged secrets, and produces a structured READY FOR REVIEW or BLOCKED report. - Use Case: Before running gh pr create on a feature branch, invoke the preflight to run type checks, lint, tests, and a full-file audit of your changes, then fix findings locally so the automated reviewer finds nothing. ## Quick Start Ask the agent to run the PR preflight check on the current branch before opening a pull request.

Frequently Asked Questions about pr-preflight

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

FAQPage Schema
How do I check my code before opening a pull request?▼

Run a preflight audit that resolves the PR base branch, lists changed files, runs your stack's type checker, linter, and tests, then reviews each changed file in full. Fix all tool failures and audit findings before pushing or creating the PR.

How to reduce back-and-forth cycles in code review?▼

Front-run the review by auditing changed files completely rather than just the diff, checking for security gaps, logic errors, dead code, and missing tests. Simulating reviewer questions locally catches issues that iterative review tools would otherwise find one at a time.

Does this preflight work with TypeScript, Bash, and Python projects?▼

Yes, it detects the stack by looking for package.json, tsconfig.json, pyproject.toml, and shell scripts, then runs only the relevant tools: tsc, ESLint, and npm tests for Node/TypeScript, ShellCheck for Bash, and Ruff or Mypy for Python.

Why does the preflight read entire files instead of just the diff?▼

Reviewers see whole files, not just changed lines, so issues like inconsistent patterns, unused imports, and broken callers often live outside the diff. Reading full files catches what diff-only review misses.

What happens when a lint or test check fails during preflight?▼

Every tool failure is treated as blocking, so the audit stops until type errors, failing tests, or ShellCheck errors are fixed. The final report marks the branch as BLOCKED rather than READY FOR REVIEW until all checks pass.