Prove that a command-line tool actually did what it said, instead of trusting its exit code and its output. Snapshots the filesystem before and after, names the expected consequence in advance, and returns one of four verdicts with what could not be seen. Use after running a build, a migration, a scaffolder, a formatter, a codegen step, or an AI coding CLI; when a command printed success and you are about to report "done"; when you are about to write "exit code 0, so it worked"; or when a tool c
Install
KitScout test notes
Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.
Similar tools
rea-analysis-optimization456,474 ★ Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserv
rea-ci-tests-audit456,474 ★ Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for s
diagnosing-bugs323,337 ★ Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or r
migrate-to-shoehorn323,337 ★ Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, w
webapp-testing194,218 ★ Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend