Stats
Actions
Tags
From cofounder
This skill should be used at the very start of every session and when the user asks to "check my environment", "run a pre-flight check", "validate setup requirements", "is my system ready", or before any cofounder project initialization. It verifies the working directory is not the home folder and no pre-existing untracked content conflicts with setup. It runs after computer-setup and before repo-setup.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cofounder:pre-flight-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate that the current environment is suitable for project initialization
Validate that the current environment is suitable for project initialization before running any other cofounder skill.
Execute the pre-flight check after computer-setup and before repo-setup. If the check fails, report the failure reasons to the user and stop — do not attempt to proceed with setup.
bash ${CLAUDE_PLUGIN_ROOT}/skills/pre-flight-check/scripts/preflight.sh
The script exits 0 and prints PREFLIGHT_PASSED on success, or exits 1 and
prints PREFLIGHT_FAILED followed by one or more error lines on failure.
Running from the user's home folder (~) risks polluting it with project files.
On failure: Recommend creating and navigating to a project subfolder first
(e.g., mkdir ~/my-project && cd ~/my-project).
When both of these conditions are true simultaneously, the check fails:
.claude and .venv.git/ does not exist)This prevents accidentally initializing a project on top of untracked existing content.
On failure: Suggest using an empty directory, or initializing a git repository first to acknowledge the existing content.
When the directory has a git repository and at least one remote is configured, the script automatically synchronizes:
This ensures every session starts from a fully synchronized state.
On failure: The script reports a GIT_SYNC_ERROR with details (commit
failed, merge conflict on pull, or push rejected). The user must resolve the
issue manually and re-run the check.
When the pre-flight check fails:
scripts/preflight.sh — Runs all environment validations and reports pass/fail with specific error codesnpx claudepluginhub gmautner/marketplace --plugin cofounderDiscovers git state, project structure, language/framework, and dev tooling in unfamiliar codebases. Provides structured summary with risk flags and recommendations for onboarding.
Initializes new Python, Rust, or TypeScript projects interactively with git repo, GitHub workflows, pre-commit hooks, Makefile, and standard configs. Updates existing projects too.
Bootstraps new projects interactively (Node/TS scripted, others manual) or adds enforcement tooling (TDD, secret scanning, file limits, git hooks, CLAUDE.md) to existing projects.