no-workarounds

Reject workaround patterns and enforce root-cause fixes in software tasks.

567|82|Updated Mar 15, 2026

Search Tags:#code quality #debugging #root cause analysis #bug fixing #technical debt #software craftsmanship

Ready to run

npx skills add https://github.com/pedronauck/skills --skill no-workarounds

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: no-workarounds
Source: https://github.com/pedronauck/skills/tree/main/skills/no-workarounds
Command: npx skills add https://github.com/pedronauck/skills --skill no-workarounds

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a rigorous approach to software development by preventing the introduction of workarounds, hacks, and symptom patches, ensuring that all fixes address the fundamental root cause of issues.

Core Features & Use Cases

Root Cause Analysis: Guides users through identifying the true origin of bugs, errors, or failures.
Workaround Detection: Actively identifies and rejects common workaround patterns like type assertions, lint suppressions, error swallowing, and timing hacks.
Use Case: When debugging a flaky test, instead of adding a setTimeout to "fix" the timing, this Skill prompts you to investigate why the test is flaky in the first place, leading to a more robust and reliable solution.

Quick Start

Activate this skill when debugging any bug or test failure to ensure you address the root cause.

Frequently Asked Questions about no-workarounds

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix flaky tests without using timing hacks or workarounds?▼

To fix flaky tests without timing hacks, perform root cause analysis to identify why the test is flaky in the first place. Investigate the true origin of the failure and reject symptom patches like setTimeout to ensure a robust, reliable solution.

What is root cause analysis in software debugging?▼

Root cause analysis in software debugging is the process of identifying the fundamental origin of bugs or failures. It enforces genuine problem resolution by detecting and rejecting common workaround patterns like type assertions, lint suppressions, and error swallowing.

How do I stop technical debt from workarounds during bug fixing?▼

To stop technical debt from workarounds during bug fixing, enforce root-cause fixes over symptom patches. Detect and reject common workaround patterns such as monkey patches, error swallowing, and lint suppressions to ensure genuine problem resolution and software craftsmanship.

Does this approach to code quality work for architectural decisions and code reviews?▼

Yes, this approach to code quality works for architectural decisions and code reviews by enforcing root-cause fixes across all software engineering tasks. It actively detects and rejects workaround patterns to ensure genuine problem resolution.

What are common workaround patterns to avoid in software engineering?▼

Common workaround patterns to avoid in software engineering include type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. Detecting and rejecting these patterns ensures fixes address the fundamental root cause rather than just symptoms.

When should I investigate the root cause instead of applying a quick patch?▼

You should investigate the root cause instead of applying a quick patch whenever you are debugging, fixing bugs, resolving test failures, or making architectural decisions. Enforcing genuine problem resolution prevents technical debt from symptom patches.