debug

Identify and fix bugs through hypothesis-driven runtime instrumentation and verification.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/CCI-Jeremy/cci-toolkit-dist --skill debug-cci-jeremy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/CCI-Jeremy/cci-toolkit-dist/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/CCI-Jeremy/cci-toolkit-dist --skill debug-cci-jeremy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams approach debugging in a structured, evidence-based way, preventing impulsive fixes and ensuring verifiable results.

Core Features & Use Cases

  • Evidence-based debug loop with runtime logs
  • Hypothesis-first investigation and instrumentation
  • Reproducible verification and cleanups
  • Browser-based testing and cross-environment validation

Quick Start

Describe a failing scenario and initiate the debug workflow to collect runtime data.

Frequently Asked Questions about debug

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

FAQPage Schema
What is evidence-based debugging and how does it improve bug fixing?

Evidence-based debugging replaces impulsive fixes by enforcing a structured workflow of hypothesis generation, runtime instrumentation, and data collection to identify and fix bugs with verifiable results.

How do I debug code using a hypothesis-first investigation workflow?

Start by describing a failing scenario to initiate the debug workflow, then generate a hypothesis, instrument the code for runtime logs, collect data, and verify the bug to ensure reproducible outcomes.

Can I use this debugging workflow for browser-based testing and cross-environment validation?

Yes, the debugging workflow explicitly supports browser-based testing and cross-environment validation, allowing you to collect runtime data and verify bugs across different codebases and environments.

What's the best way to verify a bug fix and ensure reproducible outcomes?

The best way to verify a bug fix is to follow the prescribed repeatable process of runtime logging, instrumentation, and safety checks to reproduce the scenario and confirm the fix before clean-up.

Does this debugging method support runtime logs and instrumentation across codebases?

Yes, the method streamlines debugging across codebases by providing an evidence-based debug loop with runtime logs and code instrumentation to collect necessary verification data.

Why should I use an evidence-based debug loop instead of trial-and-error fixes?

An evidence-based debug loop prevents impulsive fixes by enforcing hypothesis-first investigation, runtime data collection, and reproducible verification steps, ensuring structural bug resolution and clean-up.