rune-preflight

Validates staged code changes for logic errors, error handling, regressions, and completeness before commit.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-preflight-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-preflight
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-preflight
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-preflight-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code that compiles and passes linting can still contain logic errors, missing error handling, untested regression impact, and incomplete implementations. This Skill acts as a pre-commit quality gate that catches these "almost right" issues before they enter the repository. ## Core Features & Use Cases - Multi-Stage Code Review: Traces data flow for null dereferences and missing awaits, verifies error handling on async functions and HTTP calls, and checks boundary conditions on every changed function. - Regression and Spec Compliance: Compares the staged diff against the approved plan to detect incomplete implementations and scope creep, and traces dependent files to flag untested impact zones. - Domain Quality Hooks: Auto-detects file patterns (migrations, billing code, UI components, API contracts) and applies domain-specific checks, producing a weighted composite health score with a PASS, WARN, or BLOCK verdict. - Use Case: Before committing a new API endpoint, run preflight to confirm the endpoint has input validation, proper HTTP status codes, no swallowed exceptions, and that dependent modules still have test coverage. ## Quick Start Run preflight on my staged changes and report any logic, error handling, or regression issues before I commit.

Frequently Asked Questions about rune-preflight

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

FAQPage Schema
How do I catch logic errors in code before committing?

Run a pre-commit quality gate that traces data flow through every changed function, checking for null dereferences, missing awaits on async calls, off-by-one errors, and unsafe type coercions. Each finding is reported with file path and line number.

What should a pre-commit code review check beyond linting?

Beyond linting, check async error handling, HTTP response status validation, regression impact on dependent files, and completeness items like input validation schemas, loading states, and test coverage for new features.

How do I verify my code changes match the approved plan?

Compare the staged git diff against the plan phase by phase. Missing planned changes are flagged as blocking issues, while modifications to unplanned files are flagged as scope creep warnings.

Does pre-commit review work with React and Next.js components?

Yes, framework-specific checks apply automatically. React components with async data must have loading and error states, and Next.js Server Actions must have try/catch blocks returning typed results.

When should a pre-commit check block versus warn?

Block when findings indicate data corruption risk, security bypasses, missing planned implementations, or failing regression evals. Warn for missing error handling, untested regression zones, convention divergences, and incomplete feature items.