preflight

Detect cross-layer inconsistencies across codebase schemas, overlays, and registries.

Updated Aug 27, 2026

Search Tags:#consistency #codebase #validation #preflight #scan #cross-layer

Ready to run

npx skills add https://github.com/SameerG7/synthesis-hackathon-aibom --skill preflight-sameerg7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: preflight
Source: https://github.com/SameerG7/synthesis-hackathon-aibom/tree/main/.claude/skills/preflight
Command: npx skills add https://github.com/SameerG7/synthesis-hackathon-aibom --skill preflight-sameerg7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a pre-implementation consistency check before making codebase changes. Use before any non-trivial modification to catch pitfalls early.

Core Features & Use Cases

Detect cross-layer inconsistencies across codebase layers (schema, overlays, registries, tests, etc.).
Validate assumptions, surface stale or missing files, and guide safe edits.
Provide a deterministic, audit-friendly report of findings to prevent risky changes.

Quick Start

Run the preflight check on the target codebase area before making any non-trivial changes.

Frequently Asked Questions about preflight

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

FAQPage Schema

How do I check codebase consistency across multiple layers before making changes?▼

A cross-layer consistency scan identifies and reports synchronization issues across schema definitions, overlays, platform registries, validation constants, error handlers, and storage repositories before you make non-trivial codebase changes.

What is a preflight codebase validation scan?▼

A preflight validation scan is a deterministic, audit-friendly check that reads your current codebase state, validates assumptions, and surfaces stale or missing files across schema, registry, and test layers to prevent risky edits.

How do I detect cross-layer inconsistencies in schema definitions and registries?▼

Detect cross-layer inconsistencies by running a preflight scan that reads current states across schema definitions, overlays, platform registries, and storage repositories, validating assumptions and documenting synchronization gaps.

When do I need to run a pre-implementation consistency check?▼

Run a pre-implementation consistency check before any non-trivial codebase modification to ensure schema definitions, validation constants, error handlers, and storage repositories are synchronized, guiding safe edits.

Does a preflight scan work with existing fixtures and error handlers?▼

Yes, the preflight scan explicitly reads existing fixtures and error handlers, validating their assumptions against schema definitions and platform registries, and reporting inconsistencies to document findings for safe edits.

What are the limitations of running a preflight consistency scan?▼

The preflight consistency scan is limited to identifying and reporting inconsistencies across codebase layers before changes; it does not perform edits itself, but documents findings to guide safe modifications.