← ClaudeAtlas

recoge-tu-tiraderolisted

Use after debugging or experimentation, before final evidence or handoff, to remove residue you created that the solution does not need — trace logs, scratch files, `.only`, temporary flags, abandoned deps. NOT for the handoff gate itself; use vienen-las-visitas. NOT for unreproducible state; use por-si-se-ocupa.
mcasillas17/mexican-mom · ★ 2 · AI & Automation · score 73
Install: claude install-skill mcasillas17/mexican-mom
# A ver si ya recoges tu tiradero The bug is fixed. Everything you knocked over finding it is still on the floor. ## Rule One test governs every line you added: > **KEEP** anything that helps the next person diagnose the same **class** of failure. > **CUT** anything that only helped you diagnose **this instance**. Apply it to each added line individually. "I'll leave it, it's harmless" is not a verdict; neither is "I'll delete the whole area to be safe." **Scope: only your residue, from this work.** You may remove what you added and restore what you loosened. You may not delete pre-existing code, unrelated TODOs, someone else's commented-out block, a test you did not write, or anything that was in the tree before you started. Removing another person's work under cover of cleanup is worse than the mess — the mess is visible, and that is not. ## Procedure 1. **Diff your own changes.** Get the full diff of this work against its starting point. Cleanup you do from memory misses the file you touched an hour ago. 2. **Classify every added line** by the test above. Most rows are already decided: | What you added | Verdict | Why | | --- | --- | --- | | A test written while debugging | KEEP | It now guards the class | | A helper extracted during the fix | KEEP | It is part of the solution | | A structured log line that would diagnose this class in production | KEEP | The next person gets it for free | | Trace logging added to find the bug | CUT | It found