Debug issue

Skill MiaoY0uShan/FP/.gemini/skills/debug-issue

Finish with Proof: a portable execution protocol for coding agents—diagnose before patching, bound delegation, and verify real outcomes.

Install

npx -y skills add MiaoY0uShan/FP --skill debug-issue

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Systematically debug issues using graph-powered code navigation

SKILL.md

1.1 KB, 229 tokens by cl100k_base, as published. Nobody here has run it

Debug Issue

Use the knowledge graph to systematically trace and debug issues.

Steps

Use semantic_search_nodes_tool to find code related to the issue.
Use query_graph_tool with callers_of and callees_of to trace call chains.
Use get_flow to see full execution paths through suspected areas.
Run detect_changes_tool to check if recent changes caused the issue.
Use get_impact_radius_tool on suspected files to see what else is affected.

Tips

Check both callers and callees to understand the full context.
Look at affected flows to find the entry point that triggers the bug.
Recent changes are the most common source of 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 any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most debug triage skills give in 229 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

Investigate root cause before proposing any fixin 102 of 839, across 67 files
Read error messages completelyin 89 of 839, across 49 files
Create a failing test case before fixingin 84 of 839, across 46 files
Reproduce the issue consistentlyin 82 of 839, across 41 files
Change one variable at a timein 82 of 839, across 42 files
Check recent changesin 74 of 839, across 36 files
Write the regression test before fixingin 74 of 839, across 40 files
Fix the root cause not the symptomin 60 of 839, across 45 files
Implement a single fix at a timein 59 of 839, across 20 files
Trace data flow backward to the sourcein 50 of 839, across 20 files
Remove all debug instrumentationin 49 of 839, across 13 files
Form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

call get_minimal_context first
use detail_level minimal on all calls
use semantic_search_nodes_tool to find related code
trace call chains with query_graph_tool
view execution paths with get_flow
run detect_changes_tool to find recent changes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.