shipshitdev/execution-debugging
bundles/dev-workflow/skills/execution-debugging/SKILL.md
Scoped debugging methodology for when a test or build fails during execution/stabilization. Use to diagnose the failing check without scope-creeping — read the full error, reproduce in isolation, hypothesize before changing, localize, fix the root cause not the symptom, and guard with a regression test.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library execution-debuggingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 1, 2026, 5:01 AM86.8s2 files scanned
SKILL.md
- name:
- execution-debugging
- description:
- Scoped debugging methodology for when a test or build fails during execution/stabilization. Use to diagnose the failing check without scope-creeping — read the full error, reproduce in isolation, hypothesize before changing, localize, fix the root cause not the symptom, and guard with a regression test.
- version:
- 1.0.0
- tags:
- debugging, testing, root-cause, stabilization, regression, execution
<debugging_methodology> <scope_constraint> These steps apply ONLY to diagnosing the failing check. Do not expand beyond the files touched in the original execution. Do not redesign, refactor, or improve code outside the failure path. </scope_constraint>
When a test or build fails during stabilization, follow this sequence:
-
READ the full error output — not just the last line. Stack traces, assertion messages, and build logs contain the diagnosis.
-
REPRODUCE the failure in isolation before changing anything.
- Run the specific failing test or build step alone.
- If it passes in isolation but fails in the suite, the problem is shared state or ordering.
-
HYPOTHESIZE explicitly before each change.
- State what you believe is wrong and what evidence supports that belief.
- Do not change code "to see if it helps."
-
LOCALIZE — narrow the failure to the smallest possible scope.
- Is it in the code you wrote, or in existing code you called?
- Is it a type error, a runtime error, or a logic error?
- If it is in existing code, the plan may have an unstated assumption — surface it.
-
FIX the root cause, not the symptom.
- Suppressing an error message is not a fix.
- Adding a null check at the crash site when the upstream function should not return null is not a fix.
- Changing the test expectation to match broken behavior is not a fix.
-
GUARD — write or update a test that fails without the fix and passes with it. </debugging_methodology>
Related Skills
shipshitdev/typescript-refactor
development
VerifiedTrustedCommunity
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/typescript-expert
tools
VerifiedTrustedCommunity
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between Biome/ESLint/Turborepo/Nx.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/turborepo
tools
VerifiedTrustedCommunity
Turborepo monorepo build system guidance. Triggers on: `turbo.json`, task pipelines, `dependsOn`, caching, remote cache, the `turbo` CLI, `--filter`, `--affected`, CI optimization, environment variables, internal packages, monorepo structure, and package boundaries. Use when the user configures tasks or workflows, creates packages, sets up a monorepo, shares code between apps, runs changed packages, debugs cache behavior, or works in an `apps/` plus `packages/` workspace.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/tailwind
tools
VerifiedTrustedCommunity
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.
30SKILL.mdUpdated Jul 14, 2026