preflight

Name: preflight
Availability: InStock
Author: bonjohen

Run local GitHub Actions gate equivalents to detect build-breaking CI issues.

Updated May 14, 2026

Search Tags:#testing #linting #workflow validation #dependency checks #ci simulation #build smoke test

Ready to run

npx skills add https://github.com/bonjohen/claude-local --skill preflight-bonjohen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: preflight
Source: https://github.com/bonjohen/claude-local/tree/main/bundle/skills/preflight
Command: npx skills add https://github.com/bonjohen/claude-local --skill preflight-bonjohen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preflight reduces wasted pushes and broken builds by simulating the same checks GitHub Actions would run, locally, before changes hit CI.

Core Features & Use Cases

CI gate simulation: Runs lint/format checks, tests, workflow script existence checks, optional dependency import checks, and a build smoke test in a consistent order.
Build drift prevention: Detects missing imports, CI workflow commands that reference non-existent scripts or files, and workflow drift that would otherwise fail after pushing.
Use Case: If your team keeps seeing the same CI root causes across multiple repositories, run preflight to catch the issue in one pass and fix everything before opening the next push.

Quick Start

Run the skill in your project directory using the local preflight checks to find lint, test, workflow, dependency, and build problems before pushing.

Frequently Asked Questions about preflight

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

FAQPage Schema

How do I run local CI checks to catch build failures before pushing code?▼

Simulate CI checks locally by running linting, formatting, tests, and build smoke tests in a consistent order. This validates your code against repository gates using local equivalents before changes hit GitHub Actions.

What is workflow drift and how do I prevent it in GitHub Actions?▼

Workflow drift occurs when local environments and CI diverge, causing unexpected build failures. Prevent drift by verifying referenced workflow scripts, checking optional dependency imports, and simulating build commands locally before pushing.

Can I simulate GitHub Actions gates for Python and Node projects locally?▼

Yes, you can simulate CI gates for Python and Node projects. The validation runs local equivalents of lint, format, test, and build commands, executing Python tests via pytest to match CI behavior.

Does local preflight testing modify my project files during validation?▼

No, preflight testing enforces non-destructive read-only validation behavior. It collects failures across all gates, including missing imports and non-existent workflow scripts, without altering your source files or project configuration.

Why does my build pass locally but fail in GitHub Actions CI?▼

Builds fail in CI due to build drift, missing optional dependency imports, or workflow commands referencing non-existent scripts. Simulating these exact CI gates locally catches these discrepancies before you push.

What is the best way to check for missing dependencies before opening a pull request?▼

Run a local preflight validation that includes optional dependency import checks and build smoke tests. This detects missing imports and workflow drift in one pass, preventing broken builds after pushing.