ce-debug

Diagnose root causes of bugs and implement test-first fixes through a phased investigation workflow.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-debug-norfolk-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-debug
Source: https://github.com/Norfolk-Group/marcela-norfolk-ai/tree/main/skills/compound-engineering/skills/ce-debug
Command: npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-debug-norfolk-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Debugging often devolves into guesswork: shotgun changes, symptom fixes, and unverified hypotheses. This Skill enforces a disciplined investigation process that traces the full causal chain from trigger to symptom before any fix is proposed, so bugs are actually resolved instead of masked. ## Core Features & Use Cases - Systematic Root-Cause Investigation: Reproduces the bug, verifies environment sanity, traces the code path backward to where valid state first became invalid, and gates the fix on a complete causal chain with testable predictions. - Issue Tracker Integration: Fetches full issue threads from GitHub via gh, Linear, or Jira, including all comments, to extract reproduction steps and prior failed attempts. - Test-First Fixing with Safe Handoff: Writes a failing test before the minimal fix, runs regression suites, then commits and opens a PR with tracker auto-close syntax (e.g., Fixes #N). - Use Case: A developer pastes a stack trace or a GitHub issue URL. The Skill reproduces the failure, forms ranked hypotheses with falsifiable predictions, confirms the root cause, and delivers a tested fix on a new branch with a PR ready for review. ## Quick Start Ask the AI to debug the failing test or pasted error message and find the root cause before fixing it.

Frequently Asked Questions about ce-debug

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

FAQPage Schema
How do I debug a bug from a GitHub issue?

Provide the issue number or URL, and the Skill fetches the full thread with `gh issue view`, including all comments. It extracts reproduction steps and prior failed attempts, then proceeds through reproduction, code tracing, and root-cause confirmation.

How to find the root cause of a failing test instead of patching symptoms?

Trace backward from the error through the call chain until you find where valid state first became invalid. Form hypotheses with predictions that test a different code path, and only fix after you can explain the complete causal chain with no gaps.

Can this debug intermittent bugs that do not reproduce reliably?

Yes. The references include techniques for intermittent failures: statistical reproduction loops, logging traps, environment isolation, test-order pollution bisection, and race-condition investigation with timing isolation and condition-based waits.

What happens when multiple fix attempts keep failing?

After two to three failed hypotheses or fixes, the Skill stops and diagnoses why: scattered subsystems suggest a design problem, contradictory evidence means a wrong mental model, and environment-specific failures shift focus to config and dependency differences.

Does the debugging workflow commit changes automatically?

Only when the Skill created the branch itself. It previews the commit and PR, checks for conflicting user instructions, then runs the commit-push-PR flow with tracker auto-close syntax like `Fixes #N`. On pre-existing branches it asks first.