Name: debug-issue
Author: threnjen

Imported from threnjen/thren-agentic-workflows (ports/github/skills/debug-issue/SKILL.md). Install upstream with npx skills add threnjen/thren-agentic-workflows --skill debug-issue. Copyright stays with the author.

Debug Issue

Use the knowledge graph to trace and debug issues systematically.

Steps

Use semantic_search_nodes to find code related to the issue.
Use query_graph with callers_of and callees_of to trace the sequence of calls.
Use get_flow to trace full execution paths through suspected code.
Use detect_changes to determine whether recent changes caused the issue.
Use get_impact_radius for suspected files to identify other affected code.

Tips

Check both callers and callees to understand the full context.
Read affected flows to find the entry point that triggers the bug.
Recent changes most often cause new issues.

Token Efficiency Rules

Always start with get_minimal_context(task="<your task>") before any other graph tool.
Use detail_level="minimal" on all calls. Only escalate to "standard" when minimal is insufficient.
Target: Complete each review, debug, or refactor task in ≤5 tool calls and ≤800 total output tokens.

{ "ocm": "1", "id": "threnjen-thren-agentic-workflows-debug-issue", "kind": "skill", "name": "debug-issue", "description": "Systematically debug issues using graph-powered code navigation", "publisher": "threnjen", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Systematically debug issues using graph-powered code navigation" ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/threnjen/thren-agentic-workflows", "path": "ports/github/skills/debug-issue/SKILL.md", "ref": "fd5393ee7ac4e1ff752ab5d1f15cb1f0ac8a24da", "url": "https://github.com/threnjen/thren-agentic-workflows/blob/fd5393ee7ac4e1ff752ab5d1f15cb1f0ac8a24da/ports/github/skills/debug-issue/SKILL.md", "key": "threnjen/thren-agentic-workflows/ports/github/skills/debug-issue/SKILL.md" } }, "instructions": "## Debug Issue\n\nUse the knowledge graph to trace and debug issues systematically.\n\n### Steps\n\n1. Use `semantic_search_nodes` to find code related to the issue.\n2. Use `query_graph` with `callers_of` and `callees_of` to trace the sequence of calls.\n3. Use `get_flow` to trace full execution paths through suspected code.\n4. Use `detect_changes` to determine whether recent changes caused the issue.\n5. Use `get_impact_radius` for suspected files to identify other affected code.\n\n### Tips\n\n- Check both callers and callees to understand the full context.\n- Read affected flows to find the entry point ", "cost": { "context_tokens": 248 } }

debug-issue

About

Debug Issue

Steps

Tips

Token Efficiency Rules

Use it

Manifest

Reviews