preflight

Scan staged Git changes for secrets, debug statements, and skipped tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans staged changes to catch issues before a commit, reducing risk of leaking secrets, flaky tests, or bloated diffs.

Core Features & Use Cases

  • Detect hardcoded secrets, tokens, passwords, or private keys in staged changes.
  • Flag verbose debug output, development-only code paths, and skipped tests in the diff.
  • Provide a concise, actionable report that guides remediation before committing.

Quick Start

Run preflight to scan your current Git staging area and report potential issues before committing.

Frequently Asked Questions about preflight

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

FAQPage Schema
How do I scan staged changes for hardcoded secrets before committing?

Scanning staged changes for hardcoded secrets involves identifying tokens, passwords, or private keys in your Git diff. This process reports categorized issues without modifying files, preventing accidental data leaks in your commit.

Can I detect skipped tests and debug statements in a multi-file Git diff?

Yes, you can detect skipped tests and verbose debug output in a multi-file Git diff. The scan flags development-only code paths and disabled tests, providing an actionable report to guide remediation before you finalize the commit.

What is a preflight check for local Git worktrees?

A preflight check for local Git worktrees is a process that reviews staged versus unstaged metadata to catch risky edits. It identifies issues like large binaries or bloated diffs, reducing the risk of shipping flawed code.

Does this pre-commit scan modify my source files during analysis?

No, this pre-commit scan does not modify your source files during analysis. It reviews the staging area and outputs a categorized report of potential issues like risky edits and large binaries to guide your remediation.

What's the best way to catch flaky tests and risky edits before a Git commit?

The best way to catch flaky tests and risky edits before a Git commit is to run an automated scan on your staged changes. This flags disabled tests and risky edits, providing a concise report that guides remediation before shipping.