What problem does it solve? Starting a new session or handoff without knowing how to verify a project leads to broken assumptions and wasted setup time. This Skill discovers the safest repeatable startup and verification command for any project without assuming a specific init script exists. ## Core Features & Use Cases - Stack Signal Discovery: Scans for explicit scripts (init.ps1, init.sh, Makefile), package manager lockfiles (npm, pnpm, yarn, bun), Python files (uv.lock, pyproject.toml), and other stacks (Cargo.toml, go.mod, docker-compose.yml) in a defined priority order. - Candidate Command Mapping: Maps each detected signal to concrete candidate commands such as npm test, uv run pytest, cargo test, or go test ./.... - Structured Audit Output: Produces a Startup Path Audit report covering detected stack, baseline command, required setup, skipped checks, risks, and a recommended artifact. - Use Case: At the start of a PREVC session on an unfamiliar repository, run this Skill to identify that the project uses pnpm and establish pnpm install && pnpm test as the baseline verification command for future sessions. ## Quick Start Analyze this repository and tell me the safest baseline startup and verification command I should use at the beginning of each session.
