Fix It Never Work Around It
Stops execution and fixes root cause when commands, builds, scripts, or tools fail unexpectedly. Triggers on workaround language: 'directly', 'instead', 'alternatively', 'skip', 'fall back', 'work around', 'isn't working', 'broken', 'manually'. Activates on any unexpected non-zero exit code or process failure.
Install
/plugin marketplace add NTCoding/claude-skillzThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add NTCoding/claude-skillz --skill fix-it-never-work-around-itgit clone --depth 1 https://github.com/NTCoding/claude-skillz.git /tmp/claude-skillz
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skillz/fix-it-never-work-around-it ~/.claude/skills/fix-it-never-work-around-itPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Fix It, Never Work Around It ## Critical Rules šØ **Rule 1: Follow the prescribed process exactly.** If a step in the process fails, fix the root cause. Never skip, replace, or approximate the step. If you don't fix it, the problem recurs and all subsequent work is compromised. This does not apply to expected failures like TDD red phase ā a failing test is the process working correctly. Example: The code review subagent failed. ā "I'll review my own code and push." ā Fix why the subagent failed. šØ **Rule 2: Follow instructions exactly.** If a tool or command doesn't produce the expected result and there is no obvious alternative that produces the exact same result, stop immediately. Fix the root cause or ask for help. Never fabricate, approximate, or substitute. Example: API authentication failed. ā "I'll define some likely values instead." ā Fix the authentication or ask the user. ## Workaround Detection If you catch yourself using any of these phrases, you are about to workaround. STOP. | Workaround Signal | What You're Actually Doing | |---|---| | "Let me check via X **directly**" | Bypassing the broken tool | | "X **is broken**, let me use Y **instead**" | Abandoning the fix | | "Let me try a **different approach**" | Avoiding the actual problem | | "I'll **work around** this by..." | Literally saying it | | "**Alternatively**, we can..." | Proposing a bypass | | "Since X **isn't working**, let me..." | Giving up on fixing X |
Details
- Skill name
fix-it-never-work-around-it- Repository
- NTCoding/claude-skillz
- Path
fix-it-never-work-around-it/SKILL.md- Repo updated
- 24 March 2026
FAQ
What does the Fix It Never Work Around It skill do?
Stops execution and fixes root cause when commands, builds, scripts, or tools fail unexpectedly. Triggers on workaround language: 'directly', 'instead', 'alternatively', 'skip', 'fall back', 'work around', 'isn't working', 'broken', 'manually'. Activates on any unexpected non-zero exit code or process failure.
How do I install the Fix It Never Work Around It skill?
Claude Code plugin: /plugin marketplace add NTCoding/claude-skillz. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Fix It Never Work Around It popular?
It lives in NTCoding/claude-skillz, which has 365 GitHub stars and 47 forks.
Related skills
Architect Refine Critique
365NTCoding/claude-skillz
Three-phase design review. Chain architect ā refiner ā critique subagents. Triggers on: 'design review', 'architecture review', '/arc', system design proposals, significant refactoring decisions, new service or module design.
Challenge That
365NTCoding/claude-skillz
Force critical evaluation of proposals, requirements, or decisions by analyzing from multiple adversarial perspectives. Triggers on: accepting a proposal without pushback, 'sounds good', 'let's go with', design decisions with unstated tradeoffs, unchallenged assumptions, premature consensus. Invoke with /challenge-that.
Concise Output
365NTCoding/claude-skillz
Enforces brevity and signal-over-noise in all outputs. Eliminates verbose explanations, filler phrases, and unnecessary elaboration. Triggers on: every response (governs output length and density when loaded).
Lightweight Design Analysis
365NTCoding/claude-skillz
This skill analyzes code for design quality improvements across 8 dimensions: Naming, Object Calisthenics, Coupling & Cohesion, Immutability, Domain Integrity, Type System, Simplicity, and Performance. Ensures rigorous, evidence-based analysis by: (1) Understanding code flow first via implementation-analysis protocol, (2) Systematically evaluating each dimension with specific criteria, (3) Providing actionable findings with file:line references. Triggers when users request: code analysis, design review, refactoring opportunities, code quality assessment, architecture evaluation.
Dspy Gepa Optimizer
280intertwine/dspy-agent-skills
Optimize DSPy programs with dspy.GEPA ā a reflective/evolutionary optimizer to consider against task-specific baselines within an authorized evaluation budget. Use when the user says optimize, compile, GEPA, reflective optimization, or "make this program better" and a DSPy program + metric + trainset exist.
Lightweight Implementation Analysis Protocol
365NTCoding/claude-skillz
This skill should be used when fixing bugs, implementing features, debugging issues, or making code changes. Ensures understanding of code flow before implementation by: (1) Tracing execution path with specific file:line references, (2) Creating lightweight text diagrams showing class.method() flows, (3) Verifying understanding with user. Prevents wasted effort from assumptions or guessing. Triggers when users request: bug fixes, feature implementations, refactoring, TDD cycles, debugging, code analysis.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.