بنقرة واحدة
debug-issue
Systematically debug issues using graph-powered code navigation
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Systematically debug issues using graph-powered code navigation
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | Debug Issue |
| description | Systematically debug issues using graph-powered code navigation |
Use the knowledge graph to systematically trace and debug issues.
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>") before any other graph tool.detail_level="minimal" on all calls. Only escalate to "standard" when minimal is insufficient.Navigate and understand codebase structure using the knowledge graph
Plan and execute safe refactoring using dependency analysis
Perform a structured code review using change detection and impact
Automatically add PostHog analytics instrumentation to code. Triggers when user asks to add tracking, instrument events, add analytics, or implement feature flags in their codebase.
nuqs (type-safe URL query state) best practices for Next.js applications. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, or Next.js routing with state.