debug-issue

Name: debug-issue
Author: rahXephonz

Trace a bug/regression/panic graph-first (callers, callees, impact radius) before scanning source. Use for debug, fix, "why is X failing", root cause, crash, stack trace.

by rahXephonz(0) 0 installs

Free

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

See reviews

About

Imported from rahXephonz/diffthing (.agents/skills/debug-issue/SKILL.md). Install upstream with npx skills add rahXephonz/diffthing --skill debug-issue. Copyright stays with the author.

Debug issue

Drive the code-review-graph MCP — cheaper and more precise than broad source scanning.

get_minimal_context_tool for the symbol/file in the reported behavior.
traverse_graph_tool to walk callers and callees around it.
get_affected_flows_tool + detect_changes_tool / get_impact_radius_tool to correlate the fault with recent changes and blast radius.
Read only the source the graph points at to confirm the cause.
Reproduce with a focused test or command.
Explain root cause before editing unless the user requested a fix.

Keep graph calls minimal. Fall back to rg and focused reads when graph data is missing or stale (the graph is incremental and can lag HEAD).

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/rahxephonz-diffthing-debug-issue/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.

rahxephonz-diffthing-debug-issue.ocm.jsonjson

{
  "ocm": "1",
  "id": "rahxephonz-diffthing-debug-issue",
  "kind": "skill",
  "name": "debug-issue",
  "description": "Trace a bug/regression/panic graph-first (callers, callees, impact radius) before scanning source. Use for debug, fix, \"why is X failing\", root cause, crash, stack trace.",
  "publisher": "rahXephonz",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "skill-md",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Trace a bug/regression/panic graph-first (callers, callees, impact radius) before scanning source. Use for debug, fix, \"why is X failing\", root cause, crash, stack trace."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/rahXephonz/diffthing",
      "path": ".agents/skills/debug-issue/SKILL.md",
      "ref": "b9fc3cd869b13f3b8657a37b9f4c9f79e6d1fc4d",
      "url": "https://github.com/rahXephonz/diffthing/blob/b9fc3cd869b13f3b8657a37b9f4c9f79e6d1fc4d/.agents/skills/debug-issue/SKILL.md",
      "key": "rahXephonz/diffthing/.agents/skills/debug-issue/SKILL.md"
    }
  },
  "instructions": "# Debug issue\n\nDrive the `code-review-graph` MCP — cheaper and more precise than broad source\nscanning.\n\n1. `get_minimal_context_tool` for the symbol/file in the reported behavior.\n2. `traverse_graph_tool` to walk callers and callees around it.\n3. `get_affected_flows_tool` + `detect_changes_tool` / `get_impact_radius_tool`\n   to correlate the fault with recent changes and blast radius.\n4. Read only the source the graph points at to confirm the cause.\n5. Reproduce with a focused test or command.\n6. Explain root cause before editing unless the user requested a fix.\n\nKeep graph calls minimal. Fal",
  "cost": {
    "context_tokens": 178
  }
}

Fetch it by URL: GET /api/v1/registry/rahxephonz-diffthing-debug-issue/manifest?version=1.0.0

About

Debug issue

Use it

Manifest

Reviews