Skip to content

Instantly share code, notes, and snippets.

@portdeveloper

portdeveloper/skill.md

Created January 2, 2026 10:04
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save portdeveloper/664e1b12d1c54e026a80ce1e0f90fb4e to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save portdeveloper/664e1b12d1c54e026a80ce1e0f90fb4e to your computer and use it in GitHub Desktop.
Download ZIP
Claude Code skill: sanity-check - Detects when you're playing whack-a-mole with edge cases instead of fixing the root cause
Raw
skill.md
name description
sanity-check
Question whether the current approach is correct. Use when stuck, when a solution feels over-engineered, when playing whack-a-mole with edge cases, or when someone asks "does this make sense" or "am I on the right track" or "sanity check this".

Sanity Check

Stop. Step back. Question everything.

Questions to ask

  1. What problem are we actually solving? State it in one sentence. If you can't, that's a red flag.

  2. Are we treating symptoms instead of the cause? Signs: adding fixes one by one, each fix introduces new problems, patching around something rather than fixing it.

  3. Are we fighting a fundamental constraint? Some things can't be solved with more code. If the task violates physics/logic/math, change the constraints instead.

  4. What's the simplest thing that could work? Why isn't that good enough? Sometimes it is.

  5. What are we assuming? Which assumptions might be wrong?

Output

  1. Original problem: One sentence
  2. Current approach: One sentence
  3. Concern level: Low / Medium / High / Critical
  4. Key issue: What's wrong (if anything)
  5. Recommendation: Continue / Pivot / Stop and discuss

Be direct. If something is wrong, say so clearly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment