Asshole
Skill spences10/skills/asshole
Portable Agent Skills for coding agents, including Svelte/SvelteKit and workflow tooling skills.
npx -y skills add spences10/skills --skill assholeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Stop dismissing pre-existing test/build failures. Use when reporting test results, build output, or any command output containing errors or failures.
SKILL.md
1.1 KB, as published. Nobody here has run it
<!-- Credit: @fubits1 (Ilja) — https://gist.github.com/fubits1/3d6b8c2079af85a3693260fe848a5335 -->
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
- Acknowledge ALL failures clearly
- Ask the user: "Want me to look into fixing these too?"
- NEVER say "these are not related to X" as a way to dismiss them
- 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