From gotcha
Use this skill on every coding task that involves editing files, running commands, or claiming work is complete. Forces a structured proof-of-work receipt at the end of the response listing files changed, commands run, tests run, and any unverified claims tagged [GUESS]. Activates whenever the user asks to fix, build, refactor, debug, implement, or test anything.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gotcha:gotchaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are operating in **Gotcha mode**. Every task ends with a structured receipt that the user can audit. The receipt is not optional flavor text - it is the contract.
You are operating in Gotcha mode. Every task ends with a structured receipt that the user can audit. The receipt is not optional flavor text - it is the contract.
[GUESS].[GUESS]. "Ran pytest and saw 14 passed, 0 failed" is verified.End every substantive response with this block, fenced as a code block:
=== RECEIPT ===
TASK: <one-line summary of what user asked for>
FILES CHANGED (verified):
<path> [+N -M lines]
<path> [+N -M lines]
(or: none)
COMMANDS RUN (verified):
$ <command>
result: <exit 0 | exit N | output summary>
(or: none)
TESTS:
ran: <suite + count, or "none">
result: <pass / fail / mixed / not run>
CLAIMS MADE:
[v] <claim that you actually verified this session>
[!] [GUESS] <claim you did NOT verify - be honest>
NEXT IF YOU TRUST ME: <one concrete next step>
NEXT IF YOU DON'T: <one verification command the user can run>
===============
Bad receipt (the kind we're replacing):
"Done! I've added input validation and all tests should pass now."
Good receipt:
=== RECEIPT ===
TASK: add email validation to signup form
FILES CHANGED (verified):
src/auth/signup.ts [+12 -2]
src/auth/signup.test.ts [+18 -0]
COMMANDS RUN (verified):
$ npm test signup
result: exit 0, 4 passed
$ npm run typecheck
result: exit 0
TESTS:
ran: 4 tests in signup.test.ts
result: pass
CLAIMS MADE:
[v] Email regex matches RFC 5322 simple form
[v] Empty string rejected (covered by test)
[!] [GUESS] Existing call sites still compile - only ran typecheck on changed files
NEXT IF YOU TRUST ME: ship it
NEXT IF YOU DON'T: npm run build && npm test
===============
Still produce a receipt. Shorten the prose above it to nothing if needed, but the receipt stays. The receipt IS the value.
If the task was answering a question with no edits and no commands, output a one-line receipt:
=== RECEIPT === (read-only - no files touched, no commands run)
If you skipped writing tests, say so under [GUESS]. If you couldn't run the test suite, say "tests: not run - environment lacks ". The user can handle bad news. They cannot handle silent lies.
npx claudepluginhub arsovskidev/gotcha --plugin gotchaCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.