From bdk
Systematically debug issues using graph-powered code navigation — trace call chains, find execution paths, correlate with recent changes.
npx claudepluginhub broneq/bdk --plugin bdkThis skill is limited to using the following tools:
> Relies on BDK foundation (STARTUP_INSTRUCTIONS.md). Assumes environment discovery has already run (language, test runner, build tool are known).
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Relies on BDK foundation (STARTUP_INSTRUCTIONS.md). Assumes environment discovery has already run (language, test runner, build tool are known).
Systematically trace and debug issues using the knowledge graph.
get_minimal_context(task="debug <issue>") first.semantic_search_nodes to find code related to the issue.query_graph with callers_of and callees_of to trace call chains.get_flow to see full execution paths through suspected areas.detect_changes to check if recent changes caused the issue.get_impact_radius on suspected files to see what else is affected.get_minimal_context(task="<your task>").detail_level="minimal" on all calls. Escalate to "standard" only when minimal is insufficient.