preflight

Analyze staged code changes for logic, error handling, and regressions.

82|23|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Rune-kit/rune --skill preflight-rune-kit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: preflight
Source: https://github.com/Rune-kit/rune/tree/main/skills/preflight
Command: npx skills add https://github.com/Rune-kit/rune --skill preflight-rune-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill acts as a critical quality gate, catching code that is "almost right" – code that compiles and passes basic linting but contains subtle logic errors, missing error handling, or incomplete implementations, preventing regressions and ensuring robustness before code enters the repository.

Core Features & Use Cases

  • Logic Review: Identifies data flow errors, edge case misses, and async bugs.
  • Error Handling Verification: Ensures proper try/catch blocks, user-friendly error messages, and correct HTTP status codes.
  • Regression Prevention: Checks for compatibility issues with dependent files and identifies untested impact zones.
  • Completeness Check: Verifies new code includes necessary components like validation schemas, loading states, and tests.
  • Security Sub-Check: Integrates with the sentinel skill for security vulnerability scanning.
  • Use Case: Before committing a new feature, run preflight to automatically scan your code for potential bugs, ensure all error paths are handled, and confirm that the changes won't break existing functionality, thus maintaining a high standard of code quality.

Quick Start

Run the preflight skill to check the quality of staged code changes.

Frequently Asked Questions about preflight

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

FAQPage Schema
How do I catch logic errors and missing error handling before a git commit?▼

To catch logic errors before a commit, use a pre-commit code quality gate that analyzes data flow, edge cases, and async bugs. This process verifies proper try/catch blocks and ensures code completeness beyond standard linting.

What is the best way to prevent regressions when staging new code changes?▼

The best way to prevent regressions is to run a pre-commit check that scans for compatibility issues with dependent files. This identifies untested impact zones and enforces plan versus diff compliance before code enters the repository.

Does pre-commit hook code review check for security vulnerabilities?▼

Yes, pre-commit security checks can scan for vulnerabilities. By integrating dedicated security sub-checks, the review process identifies potential threats and ensures robustness alongside standard logic and error handling verification.

How do I verify code completeness and required components before committing?▼

To verify code completeness before committing, run a preflight check that scans your code for missing validation schemas, loading states, and tests. This ensures all necessary components are included and provides a BLOCK, WARN, or PASS verdict.

Can I use a pre-commit hook to enforce plan versus diff compliance?▼

Yes, you can use a pre-commit hook to enforce plan versus diff compliance. It analyzes staged code changes against the original implementation plan, returning a BLOCK, WARN, or PASS verdict to prevent incomplete features from entering the repository.