preflight

Validate git repository identity, remote reachability, and branch alignment before a cast.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) components.

What problem does it solve?

Verifies the working environment at the start of a cast: identity, remote, clean tree, branch divergence to prevent wasted effort from misconfigured state.

Core Features & Use Cases

  • Performs a one-time environment validation at the start of a cast to confirm repository presence, git identity, remote reachability, and branch alignment.
  • Reports the environment context, including the current branch, default branch, divergence from origin, and recent history, to guide safe modifications.
  • Outputs a JSON environment snapshot with identity, working_tree, and recent_log to enable automated checks and decision making.

Quick Start

Run the preflight script to validate your repository state before starting a cast.

Frequently Asked Questions about preflight

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

FAQPage Schema
How do I verify my git environment before starting automated repository modifications?▼

Verifying your git environment before modifying a repository involves checking repository presence, identity configuration, remote reachability, and branch alignment. This preflight validation outputs a JSON snapshot to confirm the state and prevent proceeding with incorrect assumptions.

What is preflight validation for a git workflow and why is it needed?▼

Preflight validation for a git workflow is a one-time check that confirms repository presence, git identity, and remote reachability. It is needed to prevent wasted effort from misconfigured states, ensuring hard failures for missing identity or unreachable remotes before modifications begin.

How do I check git branch divergence and working tree status before a commit?▼

Checking git branch divergence and working tree status requires validating the current branch against the default branch and origin. This process reports a clean tree state and recent history, outputting a JSON environment snapshot to guide safe modifications.

Does the preflight git validation require jq and git dependencies?▼

Yes, the preflight git validation requires both jq and git dependencies. It uses jq to parse the JSON environment snapshot containing identity, working_tree, and recent_log data, while git is used to validate the repository state and branch alignment.

What happens if my git remote is unreachable or my identity is missing during environment validation?▼

If your git remote is unreachable or your identity is missing, environment validation triggers hard failures. This prevents the workflow from proceeding with incorrect assumptions, ensuring that fetch failures and missing identity configuration are caught before any repository modifications start.

Can I automate git branch creation and remote fetch checks in one step?▼

Yes, you can automate git branch creation and remote fetch checks in one step using a preflight script. It validates remote accessibility, handles branch divergence from origin, and ensures correct branch alignment before proceeding with repository modifications.