readylisted

# Ready Leave the repository with one unattended command that returns a meaningful exit code, plus only the guardrails needed for future agents to self-verify. Detect the stack; do not assume it. Run every artifact you add. ## 1. Detect Run the bundled scan first: ``` <this-skill-dir>/scripts/detect.sh <repo-root> ``` It finds candidates, not truth; open flagged files and interpret CI matrices or unusual build systems yourself. Inspect in this order: 1. CI config: use what CI runs. 2. Manifests and runners: package scripts, pyproject/tox/nox, Make/just, Cargo/go/Gradle/composer. 3. README, CONTRIBUTING, CLAUDE.md, AGENTS.md, and docs; record docs/CI drift. 4. Existing test directories and naming conventions. Report run/test/lint/typecheck/build/git as command or `MISSING`. If this is not a Git repository, propose `git init` but ask first. ## 2. Establish verification Reuse the existing verify path. If none exists, create the smallest entrypoint in the repository's native convention. The command must: - exit non-zero on failure and run unattended; - work offline without credentials, GPU, network, or secrets; - use installed project tooling and avoid watch mode; - stay quiet on success and be documented for humans. Time it once. Use one tier when the suite is already quick. When slow checks would cripple the edit loop, define: - `verify`: lint/typecheck/unit or smoke coverage, normally under ~60 seconds; - `verify-full`: integration/build/slow coverage, required