Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

asshole

Étoiles35

Forks2

Mis à jour24 avril 2026 à 19:22

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

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

spences10

spences10/claude-code-toolkit

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

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

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

Plus depuis ce dépôt

même dépôt

mcp-setup

spences10/claude-code-toolkit

Setup guide for essential MCP servers. Use when configuring MCP servers or when user asks about search, SQLite, or MCP management.

2026-04-2435

analytics

spences10/claude-code-toolkit

Query Claude Code session analytics from ccrecall database. Use when user asks about token usage, session history, or wants to analyze their Claude Code usage patterns.

2026-04-2435

advanced-prompting

spences10/claude-code-toolkit

High-leverage prompts that challenge Claude's defaults. Use for "grill me", "prove it works", "scrap this", "what would 10x engineer do", "find ways this fails".

2026-04-2435

claude-md-maintenance

spences10/claude-code-toolkit

Maintain CLAUDE.md files effectively. Use when adding lessons learned, updating conventions, or restructuring project instructions.

2026-04-2435

orchestration

spences10/claude-code-toolkit

Multi-agent orchestration patterns for Claude Code team mode. Use when coordinating teammates, decomposing complex tasks, or managing shared task lists.

2026-04-2435

structured-rpi

spences10/claude-code-toolkit

Enhanced Research-Plan-Implement workflow with structured phase gates. Use when tackling complex tasks that benefit from a phased approach with user checkpoints.

2026-04-2435

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

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