Skip to main content
Generalspences10

asshole

Stop dismissing pre-existing test/build failures. Use when reporting test results, build output, or any command output containing errors or failures.

Stars
33
Source
spences10/claude-code-toolkit
Updated
2026-04-29
Slug
spences10--claude-code-toolkit--asshole
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/spences10/claude-code-toolkit/HEAD/plugins/devops-skills/skills/asshole/SKILL.md -o .claude/skills/asshole.md

Drops the SKILL.md into .claude/skills/asshole.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Asshole

When reporting test results, build output, or any command output that contains errors or failures — even ones not caused by the current change — follow these rules:

Rules

  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 dismiss 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.

Anti-patterns

  • Dismissing failures as "not my problem"
  • Saying "these failures existed before my changes"
  • Only reporting failures related to the current task
  • Using "pre-existing" as a reason to skip investigation