bostonaholic/skills

fixing-root-causes

Traces a bug or failure to its root cause and fixes it there instead of patching the symptom.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/bostonaholic/skills --skill fixing-root-causes

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Fix Root Causes

When debugging, do not fix symptoms. Trace every problem to its root cause and fix it there.

Why: Symptom fixes accumulate. Each workaround makes the system harder to reason about, and the real bug remains. Root-cause fixes are slower upfront but reduce total debugging time.

Pattern:

  • Reproduce first
  • When docs and code disagree, decide which is the bug per the docs and code rules
  • Ask "why" until you hit the root cause
  • Do not add guards (adding a nil check to silence a crash is a symptom fix)
  • If a workaround needs a paragraph-long comment to justify it, the code is wrong (fix the code, not the comment)
  • Check for the pattern, not just the instance (grep for the same pattern, fix all instances)
  • When stuck, instrument. Don't guess (add logging, read the actual error)

Restart bugs: suspect state before code

When something "fails after restart," suspect stale persistent state first: config files, caches, lock files, serialized state. If clearing a state file restores behavior, prioritize state validation as the fix.

from this repository

More skills

All skills
bostonaholic
Community

auditing-agent-token-usage

Audits recent Claude Code and Codex session logs for token and context cost: model routing, inherited subagent models, long sessions, compactions, oversized tool results, and unused MCP servers. Use when the user says \"audit token usage\", or when asked about agent token usage, context costs, session length, model routing, or cost efficiency.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

auditing-complexity

Ranks where code complexity concentrates in a git repository (cyclomatic complexity, nesting, fan-out, mutable state) and scores CRAP change risk from a coverage file. Read-only. Use when the user says "find complexity hotspots", or when asked for complexity hotspots or change risk. Not for test value; use auditing-tests.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

auditing-tests

Audits a test suite, or a named part, for low-value tests and marks each retain, fix, consolidate, or delete with verified removal evidence. Read-only. Use when the user says "audit the tests", or when asked to audit tests for redundant, junk, or low-value tests. Not for code complexity; use auditing-complexity.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

being-extremely-fucking-brief

Keeps every reply to the user to three lines or fewer, with no preamble, restated question, recap, or closing offer. Use when the user says "be brief", or when about to reply to the user: load it before every reply in every session, including plain questions, recommendations, and comparisons, even when no other skill applies. Load it alongside any other skill that fits the request, never instead of one.

1h installs
1
GitHub stars
2
Updated
Nov 21