pr-preflight

Enforce a thirteen-step PR preflight gate for Next.js and Supabase projects.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/speqqai/claude --skill pr-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-preflight
Source: https://github.com/speqqai/claude/tree/main/skills/pr-preflight
Command: npx skills add https://github.com/speqqai/claude --skill pr-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This preflight automation ensures every required PR gate passes before a merge, reducing manual checks and human error.

Core Features & Use Cases

  • Automated Step Gate: enforces a thirteen-step pass/fail gate covering env, security, types, build, lint, Next.js, Supabase, multi-tenant, custom code audit, performance, tests, diff review, and submit.
  • PR Readiness & Auto-Submission: submits a PR to the dev branch automatically when all steps pass.
  • Guided Workflow: provides structured steps and checklists to guide engineers through PR readiness.

Quick Start

Run the preflight to verify PR readiness before submitting.

Frequently Asked Questions about pr-preflight

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

FAQPage Schema
How do I automate pull request quality checks for Next.js and Supabase?

Automate pull request quality checks by enforcing a thirteen-step preflight gate that validates environment, security, types, build, lint, Next.js, Supabase, multi-tenant, code audit, performance, tests, diff review, and submit before merging.

What steps are included in a PR preflight gate for TypeScript projects?

A PR preflight gate for TypeScript projects includes sequential validation across environment, security, types, build, lint, Next.js, Supabase, multi-tenant, custom code audit, performance, tests, diff review, and submit to ensure consistent quality.

Can I automatically submit a PR to the dev branch after passing checks?

Yes, you can automatically submit a PR to the dev branch when all thirteen preflight steps pass, reducing manual intervention and ensuring only verified code is merged.

Does this preflight workflow support multi-tenant Supabase validations?

This preflight workflow supports multi-tenant Supabase validations by including a dedicated step within its thirteen-step gate to verify multi-tenant configurations before PR submission.

When do I need to run a PR preflight check in my workflow?

You need to run a PR preflight check when triggers fire on PR events like open, submit, or push, ensuring all required quality gates pass before merging into the dev branch.

What is the best way to enforce consistent PR quality gates across repositories?

The best way to enforce consistent PR quality gates is applying a deterministic, thirteen-step preflight workflow that covers env, security, types, build, lint, Next.js, Supabase, multi-tenant, code audit, performance, tests, diff review, and submit.