I replayed 7 repos' READMEs in fresh clones. 2 of them fail their own quickstart.

Description and use

Testing README instructions in fresh clones revealed that 2 of 7 repositories have broken quickstart steps.

Problem

README setup instructions often become outdated, causing new users to fail at the quickstart.

Outcome

Out of 7 repositories tested, 2 had README quickstarts that failed when replayed in a fresh clone; the tool identified missing npm start scripts and other inconsistencies.

Workflow

• Clone repository into a temporary directory without node_modules, .env, or untracked files.
• Parse shell commands from the README in order.
• Execute each command, tracking working directory and environment.
• If a command fails, capture exit code, last output lines, and the README line that caused it.
• Report all failures to the user.
• Optionally run in a Docker container for a clean environment.
• Perform static checks before execution (e.g., missing npm scripts, mismatched package managers, unsafe curl|bash installers).

Evidence

coldstart stages your committed state in a temp dir. No node_modules, no .env, none of the untracked files that make it work on your machine and nowhere else.

Source

When a step fails, you get the exit code, the last output lines, and the exact README line that sent a new user there.

Source

7 repos, 2 fail their own quickstart.

Source