Skip to content
OpenSmartRoute
Skillv1.0.0

execution-debugging

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, hypo

by shipshitdev(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from shipshitdev/skills (skills/execution-debugging/SKILL.md). Install upstream with npx skills add shipshitdev/skills --skill execution-debugging. Copyright stays with the author.

<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. </debugging_methodology>

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/shipshitdev-skills-execution-debugging/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

shipshitdev-skills-execution-debugging.ocm.jsonjson
{
  "ocm": "1",
  "id": "shipshitdev-skills-execution-debugging",
  "kind": "skill",
  "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.",
  "publisher": "shipshitdev",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "medical"
    ],
    "tags": [
      "skill-md",
      "debugging",
      "testing",
      "root-cause",
      "stabilization",
      "regression",
      "execution",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "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."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/shipshitdev/skills",
      "path": "skills/execution-debugging/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/shipshitdev/skills/blob/HEAD/skills/execution-debugging/SKILL.md",
      "key": "shipshitdev/skills/skills/execution-debugging/SKILL.md"
    }
  },
  "instructions": "<debugging_methodology>\n<scope_constraint>\nThese steps apply ONLY to diagnosing the failing check.\nDo not expand beyond the files touched in the original execution.\nDo not redesign, refactor, or improve code outside the failure path.\n</scope_constraint>\n\nWhen a test or build fails during stabilization, follow this sequence:\n\n1. READ the full error output — not just the last line. Stack traces, assertion messages, and build logs contain the diagnosis.\n\n2. REPRODUCE the failure in isolation before changing anything.\n   - Run the specific failing test or build step alone.\n   - If it passes in iso",
  "cost": {
    "context_tokens": 374
  }
}

Fetch it by URL: GET /api/v1/registry/shipshitdev-skills-execution-debugging/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.