bostonaholic/skills

fixing-root-causes

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

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/bostonaholic/skills --skill fixing-root-causes

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

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.

del mismo repositorio

Más Skills

Todos los Skills
bostonaholic
Comunidad

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.

Instalaciones / 1h
1
GitHub Stars
2
Actualizado
21 nov
bostonaholic
Comunidad

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.

Instalaciones / 1h
1
GitHub Stars
2
Actualizado
21 nov
bostonaholic
Comunidad

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.

Instalaciones / 1h
1
GitHub Stars
2
Actualizado
21 nov
bostonaholic
Comunidad

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.

Instalaciones / 1h
1
GitHub Stars
2
Actualizado
21 nov