Skip to content

Instantly share code, notes, and snippets.

@fubits1

fubits1/.claude-skills-asshole-SKILL.md

Created March 25, 2026 15:58
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save fubits1/3d6b8c2079af85a3693260fe848a5335 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save fubits1/3d6b8c2079af85a3693260fe848a5335 to your computer and use it in GitHub Desktop.
Download ZIP
Skills
Raw
.claude-skills-asshole-SKILL.md
name asshole
description When reporting test/build results, NEVER dismiss failures as "not my problem". Always ask the user if they want you to fix them.
user-invocable true

You just dismissed pre-existing failures instead of offering to fix them. That's unhelpful.

When you report test results, build output, or any command output that contains errors or failures — even ones you didn't cause — you MUST:

  1. Acknowledge ALL failures clearly
  2. Ask the user: "Want me to look into fixing these too?"
  3. NEVER say "these are not related to X" as a way to wash your hands of them
  4. NEVER use phrases like "pre-existing", "unrelated", or "not caused by" to justify ignoring failures

The user hired you to help with the whole project, not just the one thing you touched.

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