apex:debug

Automates Cypher-based debugging workflows with-Aware AI-powered root cause analysis.

3|1|Updated Jul 2, 2025
One-click install
npx skills add https://github.com/benredmond/apex --skill apex-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apex:debug
Source: https://github.com/benredmond/apex/tree/main/skills_backup/20260112-223111/skills/debug
Command: npx skills add https://github.com/benredmond/apex --skill apex-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with APEX pattern learning provides a disciplined, evidence-driven workflow to identify root causes, reducing time spent on debugging and preventing repeated failures.

Core Features & Use Cases

  • Evidence-based hypothesis generation and testing aligned with APEX patterns.
  • Integration with failure-predictor and git-historian to surface historical context.
  • Structured recording of reproduction steps, evidence, and reflections to improve future debugging sessions.
  • Phase-agnostic debugging across the software lifecycle.

Quick Start

To start a debugging session, issue the apex:debug command and provide a short error description or task ID.

Frequently Asked Questions about apex:debug

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

FAQPage Schema
What is hypothesis-driven debugging and how does pattern learning work?

Hypothesis-driven debugging systematically generates and tests root-cause hypotheses using evidence collection. APEX pattern learning records reflections from each session to improve future debugging efficiency and prevent repeated software failures.

How do I start a systematic debugging session with APEX?

To start a debugging session, issue the apex:debug command and provide a short error description or task ID. The workflow then automates evidence collection, hypothesis generation, and structured reflection aligned with APEX patterns.

Can I use this debugging workflow across different software lifecycle phases?

Yes, this hypothesis-driven debugging workflow is phase-agnostic and can be applied across the software lifecycle. It systematically collects evidence and records reproduction steps regardless of the development stage.

What's the best way to find root causes using evidence-driven debugging?

The best way to find root causes is evidence-based hypothesis generation and testing aligned with APEX patterns. Integrating failure-predictor and git-historian surfaces historical context to accelerate systematic debugging.

Why do I keep hitting the same software bugs and can debugging reflections prevent this?

Repeated software failures are prevented by structured recording of reproduction steps, evidence, and debugging reflections. APEX pattern learning applies these past insights to improve future root-cause analysis sessions.