← ClaudeAtlas

isitdonelisted

Prove a coding task is actually done before saying so. Runs the repository's real test, typecheck and lint commands on the exact working tree, writes a git-bound receipt, and reports NOT DONE with the failing output when anything fails. Use it before claiming "tests pass", before opening a PR, at the end of any task that changed code, or when a user asks you to verify your work.
raimondasl/isitdone · ★ 1 · Code & Development · score 72
Install: claude install-skill raimondasl/isitdone
# isitdone `isitdone` is a zero-dependency CLI that answers one question: **do this repository's own checks pass on the code as it is right now?** It never guesses. It runs `npm test`, `pytest`, `go test`, `cargo test`, `tsc`, `ruff`, `eslint` (whatever the repo defines) in a subprocess and reads the exit codes. ## When to run it - Before you write "done", "complete", "all tests pass", "verified", "ready for review", or similar. - After every change that could affect behaviour, even if you only "fixed a typo". - When the user asks whether the work is finished or whether tests pass. - As the last step before creating a commit or pull request. ## How to run it ```bash npx isitdone ``` - Exit code `0` and a line starting with `DONE` mean every detected check passed on this exact tree, and a receipt was written to `.isitdone/receipt.json`. - Exit code `1` and `NOT DONE` mean at least one check failed. The output shows which command failed and the last lines of its output. - If it prints `no checks detected`, tell the user; do not claim the tests pass, because nothing ran. Machine-readable form for scripts and orchestrators: ```bash npx isitdone --json # {"ok": true|false, "done": true|false, "checks": [...]} ``` ## What to do with the result 1. **NOT DONE**: fix the underlying problem and run `npx isitdone` again. Do not delete, skip, `.only`, `xit`, or weaken tests, and do not change test configuration or CI settings to make the check pass. If you believe a check