No Workarounds

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 118e61cf1c61 · 16 Oct 2026Report an issue or request a re-scan

• Publisherpedronauck GitHub userOwner of the repository this skill is read from
• Source folderpedronauck/skills/skills/mine/no-workaroundsThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict118e61cf1c61A new audit runs when the source changes
• Repository statusNot archivedLast push 31 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Evaluate a proposed fix that suppresses errors, diagnostics, or symptoms. Use for suspected workarounds and unavoidable external defects; not as a mandatory stage for every bug fix.

---
name: no-workarounds
description: Evaluate a proposed fix that suppresses errors, diagnostics, or symptoms. Use for suspected workarounds and unavoidable external defects; not as a mandatory stage for every bug fix.
metadata:
  author: Pedro Nauck
  github: https://github.com/pedronauck
  repository: https://github.com/pedronauck/skills
---

# Fix the Source

Use this skill when a proposed repair suppresses a diagnostic or hides a failure instead of correcting it. Start from the evidence already collected; use `systematic-debugging` only when the cause remains unclear.

- Trace the observed failure to its owning code or boundary. Correct that cause and verify the original symptom in the existing owning suite or probe.
- Review casts, suppressions, swallowed errors, fixed sleeps, monkey patches, and fallback chains in context. These are investigation signals, not proof that every occurrence is wrong. Read the matching entry in `references/workaround-catalog.md` when needed.
- Preserve intentional boundary validation, typed failure handling, and compatibility migrations/adapters required by project policy. A documented deprecation window is a product contract.
- Keep the repair focused; reuse suitable utilities and avoid unrelated architecture cleanup.

## External Defects

When the defect is outside the team's control, isolate the necessary adapter at the boundary, explain the evidence and removal condition, and use the existing suite to protect the affected behavior. Reference an existing upstream issue where available; create external issues only when authorized. Add a canary or review date only if it can reliably detect expiry and earns its maintenance cost.

Complete when the original failure is corrected or the bounded external limitation is explicit, and the relevant checks pass. Reuse current results; neither a whole catalog read nor a separate written gate is required for every fix. `references/philosophical-foundations.md` is optional rationale.

Excerpt, first 1,991 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/pedronauck/skills
git -C skills checkout 118e61cf1c61

Works in

1. 2026-10-16
   ✓SAFE B 89 / 100

   first audit · source 118e61cf1c61

Questions about No Workarounds

• github.com/pedronauck/skills/tree/main/skills/mine/no-workaround — the audited source at commit 118e61cf1c61 and every finding aboveObserved · 16 Oct 2026

Spotted something wrong? Report a correction · Methodology