Pre-Flight Check

Validate working directory and detect untracked content before project initialization.

3|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/gmautner/marketplace --skill pre-flight-check-gmautner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Pre-Flight Check
Source: https://github.com/gmautner/marketplace/tree/main/plugins/cofounder/skills/pre-flight-check
Command: npx skills add https://github.com/gmautner/marketplace --skill pre-flight-check-gmautner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The pre-flight check helps ensure that every project session starts in a clean, safe environment by validating that you are not in the home directory and that there are no conflicting untracked files when a Git repository has not yet been initialized. It runs after computer-setup and before repo-setup to enforce proper setup order and prevent accidental overwrites.

Core Features & Use Cases

  • Environment validation: ensures the current directory is not the home folder.
  • Conflict detection: detects pre-existing content when there is no local Git repository.
  • Guardrail enforcement: aborts setup with clear guidance when validations fail.
  • Use case: initialize a new cofounder project in a dedicated workspace to avoid polluting your home directory or existing content.

Quick Start

Run the pre-flight check at the start of a session to verify your environment and avoid conflicts.

Frequently Asked Questions about Pre-Flight Check

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

FAQPage Schema
How do I check my project environment before initializing a git repository?

To check your project environment before initializing a git repository, run a pre-flight validation to ensure the working directory is not your home folder and detect any conflicting untracked files.

Why should I validate my working directory before project initialization?

Validating your working directory before project initialization prevents accidental overwrites and avoids polluting your home folder with project files when a local Git repository does not yet exist.

What happens if environment validation fails during project setup?

If environment validation fails during project setup, the process aborts immediately and exits with clear error messages, providing guidance to resolve issues like being in the home directory or having untracked content.

When do I run environment validation in my project setup workflow?

You run environment validation at the start of every session, specifically after computer-setup and before repo-setup, to enforce the required execution order and ensure a clean workspace.

Can I initialize a new project if there are pre-existing untracked files in the directory?

You cannot initialize a new project safely if pre-existing untracked files are detected in a directory without a local Git repository, as the pre-flight check will flag this conflict and abort the setup.

Does the pre-flight check stop setup if I am working from my home folder?

Yes, the pre-flight check stops the setup if you are working from your home folder, enforcing guardrails by aborting the process with clear errors to prevent accidental file overwrites.