Prove It Ran
Verify that tests, builds and checks actually ran and exercised the changed code, before claiming a task is done. Use before reporting completion, or when asked to prove tests ran or verify a fix.
Install
npx skills add agentkitco/agentkit-dev-skills --skill prove-it-rangit clone --depth 1 https://github.com/agentkitco/agentkit-dev-skills.git /tmp/agentkit-dev-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agentkit-dev-skills/skills/prove-it-ran ~/.claude/skills/prove-it-ranPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Prove it ran
Goal: never say "done" or "tests pass" on the strength of belief. Show evidence that the checks ran, covered the change, and would have caught a failure.
## Procedure
1. **List the claims** you are about to make ("the bug is fixed", "all tests pass", "the build succeeds", "no lint errors").
2. **For each claim, run the command now**, from a clean state of your edits, and capture the output. Do not rely on output from earlier in the session if you edited files since.
3. **Confirm the check really ran:**
- Test runners: the output shows a test count above zero, and the new or changed tests appear by name or file. "0 tests", "no tests found" or "skipped" is not a pass.
- Check the exit code, not just the wording (`echo $?` right after the command, or the runner's summary line).
- Make sure the runner picked up your files: right directory, right config, test file matches the naming pattern.
4. **Confirm it covers the change.** For a bug fix, the test must fail without the fix: temporarily revert the fix (`git stash` the source change only, or comment it out), run the test, see it fail, restore, see it pass. If you cannot do this, say so.
5. **Check for silent skips.** Search output for `skipped`, `xfail`, `pending`, `todo`, and your own `.only`/`.skip`/`pytest.mark.skip` leftovers (`rg "\.only\(|\.skip\(|xit\(|fdescribe|pytest.mark.skip"`).
6. **Run the wider checks** the project defines (lint, type check, build). Report exact commands.Details
- Skill name
prove-it-ran- Repository
- agentkitco/agentkit-dev-skills
- Path
skills/prove-it-ran/SKILL.md- License
- MIT
- Repo updated
- 29 October 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Prove It Ran skill do?
Verify that tests, builds and checks actually ran and exercised the changed code, before claiming a task is done. Use before reporting completion, or when asked to prove tests ran or verify a fix.
How do I install the Prove It Ran skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add agentkitco/agentkit-dev-skills --skill prove-it-ran. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Related skills
Test Checklist
Ifeanyiejindu/qarunbook
Build a complete QA test plan for an app — every module, feature and user journey, across each platform it runs on. Use when asked for a test plan, QA checklist, test cases, regression suite, or "what should we test", or when preparing an app for QA, a release or a demo. Writes the plan, puts it into qarunbook (creating the app, or adding to it), then offers to start testing it straight away.
Keyboard Shortcuts
nparashar150/claude-keyboard-shortcuts
Audit a web app for missing keyboard shortcuts and implement them end to end: a command registry, context-scoped bindings, a command palette, visible kbd hints, a ? help sheet, invariant tests, and WCAG 2.1.4 compliance. Use whenever the user mentions keyboard shortcuts, hotkeys, keybindings, a command palette, Cmd+K, power-user features, or making an app feel fast, and also when building or reviewing any list, table, modal, form, or editor UI where shortcuts and keyboard access obviously belong even if the user never says the word shortcut.
Watch
igamingsychov/watch-igaming
Смотрит любое видео - по ссылке (видеохостинг, запись экрана или встречи, прямой mp4) или локальный файл (.mov/.mp4) - не только читает транскрипт, но и видит, что на экране. Кадры берёт по сменам сцен (ffmpeg scene detection), а не по таймеру, поэтому не пропускает графику, демо, монтаж и b-roll. Звук: субтитры через yt-dlp, fallback - локальная расшифровка речи. Результат - разбор или таблица в нужном формате: QA-таблица, сравнение конкурентов, UX-аудит, протокол созвона, конспект лекции. Используй, когда пользователь пишет /watch <url> или просит «посмотри это видео», «разбери ролик/созвон/
Grill
1mtangoz/grill
Grill a decision, plan or forecast. An outside AI judge, a model from a different company than Claude, argues the strongest case for and against it, names the cheapest test that would settle each challenge, and gives a verdict. Use when the user says grill, stress-test, pressure-test, poke holes in, red-team or challenge something they decided or plan to decide, when the weekly review marks a decision for grilling, or when they say look back or paste a decision record to score.
Wreck It
miyannishar/wreck-it
Full wreck-it run against a locally running web app. It tests like normal users, ICP personas, rushed beginners, chaos monkeys and traffic spikes, then writes a scored bug report with source file:line and regression Playwright tests. Use when the user says "wreck my app", "wreck it", "test my app like a user", "find bugs before launch", "is my app ready to ship", or asks for a readiness score. Also for one feature, such as "test the checkout", "just test signup", "check the coupon flow" (a focused run). For a single stage ("just stress test my API", "only check accessibility"), use the matchin
Never Again
1malaysherasia-ai/claude-never-again
Capture a bug or mistake as a permanent guardrail so it cannot happen twice. Use this skill whenever a bug is fixed, a test fails and is repaired, the user says "you did that again", "don't do that", "remember this", "never do X", or any correction is made that a future session would otherwise forget. Also use when the user asks to review, promote, or clean up existing lessons and hooks.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.