execution-debugging

Included with Lifetime

$97 forever

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.

Code Review

What this skill does


<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:

1. READ the full error output — not just the last line. Stack traces, assertion messages, and build logs contain the diagnosis.

2. 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.

3. 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."

4. 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.

5. 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.

6. GUARD — write or update a test that fails without the fix and passes with it.
   - This prevents the same failure from recurring in future stabilization cycles.
</debugging_methodology>

Files: 2

Size: 2.3 KB

Complexity: 14/100

Category: Code Review

Source: https://github.com/shipshitdev/library/tree/main/bundles/dev-workflow/skills/execution-debugging

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts