gxpm-debug-issue

Name: gxpm-debug-issue
Availability: InStock
Author: laozhong86

Trace failures through a knowledge graph to identify root causes.

1|Updated Apr 24, 2026

Search Tags:#debugging #troubleshooting #root-cause #software-engineering #knowledge-graph #code-navigation

Ready to run

npx skills add https://github.com/laozhong86/gxpm --skill gxpm-debug-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gxpm-debug-issue
Source: https://github.com/laozhong86/gxpm/tree/main/skills/gxpm-debug-issue
Command: npx skills add https://github.com/laozhong86/gxpm --skill gxpm-debug-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic diagnosis of software failures by tracing issues through a knowledge graph to identify root causes, rather than guessing from symptoms.

Core Features & Use Cases

Graph-driven navigation to inspect callers, callees, and related processes to locate the origin of a bug.
Stepwise diagnosis loop including load gxpm-diagnose, explore code structure with gxpm-explore-codebase, and safe refactor guidance with gxpm-refactor-safely.
Verification and evidence gathering with deterministic steps and recoverable state to ensure auditability.

Quick Start

Ask me to start a diagnosis by loading /gxpm-diagnose to trace a failing test to its origin.

Frequently Asked Questions about gxpm-debug-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find the root cause of a failing test by tracing code execution flows?▼

Graph-driven debugging traces failing tests through a knowledge graph of callers and callees to identify the root cause. It navigates code structure across repositories using deterministic steps and verifiable evidence instead of guessing from symptoms.

What is the best way to systematically debug unknown performance regressions across a codebase?▼

The best way to debug performance regressions is systematic diagnosis through a knowledge graph. This approach inspects related execution flows across repositories, applying deterministic steps and recoverable state to ensure auditability while locating the origin.

How do I start a systematic diagnosis loop for an unknown software failure?▼

Start a systematic diagnosis loop by loading the gxpm-diagnose capability to trace the issue. Follow stepwise procedures to inspect code structure and gather verifiable evidence with deterministic steps to locate the bug's origin.

Does graph-powered debugging work for diagnosing issues across multiple repositories?▼

Graph-powered debugging works across multiple repositories by tracing execution flows through a unified knowledge graph. It applies systematic diagnosis to inspect code structure and identify root causes for unknown symptoms and failing tests in diverse codebases.

Can I verify the evidence when tracing a bug's root cause through a knowledge graph?▼

You can verify evidence when tracing a bug's root cause because the diagnosis process provides deterministic steps and recoverable state. This ensures auditability and systematic validation of the identified origin of software failures.