Set a repo up to prove engineering-task work actually works before it ships. Investigates the repo, ensures a one-command dev stack (`dev-local`) exists, asks whether verification runs locally or in a sandbox (crabbox), confirms/installs the driver (the `playwright-cli` skill for web by default). Outputs three artifacts: a committed `/verify` skill (per-task verification SOP — spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded), the `/dev-loca
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