skills.rest
JNZader
JNZaderCOMMUNITY
Explore all skills by this author →
GitHub

debug-mode

Automate hypothesis-driven debugging with tagged logs and automated cleanup.

Updated Mar 15, 2026
Search Tags:#automation#debugging#logging#cleanup#instrumentation#hypothesis
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill debug-mode-jnzader
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-mode
Source: https://github.com/JNZader/javi-ai/tree/main/own/skills/debug-mode
Command: npx skills add https://github.com/JNZader/javi-ai --skill debug-mode-jnzader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Provides a structured approach to debugging by enabling hypothesis generation, instrumented traces, and automated cleanup to ensure reproducible fixes.

Core Features & Use Cases

  • Hypothesis-driven debugging: Generates and tests hypotheses with tagged logs mapped to each hypothesis.
  • Instrumented tracing: Injects region-tagged logs and writes them to a persistent log for analysis.
  • Automated cleanup: Removes all instrumentation blocks and debug artifacts once verification is complete.

Quick Start

Initiate a debugging session following the protocol to reproduce the bug and produce structured instrumentation plus automatic cleanup.

Frequently Asked Questions about debug-mode

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

FAQPage Schema
How do I automate hypothesis-driven debugging to trace software failures?▼

You automate hypothesis-driven debugging by generating testable assumptions, injecting region-tagged logs, and writing traces to a persistent file for analysis. This structured workflow systematically investigates bugs and diagnoses unexpected behavior.

What is the best way to remove debug instrumentation and logging after a fix?▼

The best way to remove debug instrumentation is using an automated cleanup script that eliminates all injected blocks and debug artifacts once verification is complete. This ensures reproducible fixes without leaving residual tracing code.

Can I use this structured debugging workflow across different software projects?▼

Yes, you can apply this structured debugging workflow across different software projects to investigate bugs, trace failures, or diagnose unexpected behavior. It requires region-tagged logs, a persistent debug file, and a cleanup script.

How does region-tagged logging work for diagnosing unexpected behavior?▼

Region-tagged logging works by injecting markers into code that map directly to specific debugging hypotheses. These isolated logs are written to a persistent file, allowing you to trace failures and analyze unexpected behavior systematically.

Do I need a persistent log file to investigate bugs with this debugging approach?▼

Yes, you need a persistent log file at the designated debug path to store region-tagged traces during your debugging session. This file captures the isolated instrumentation needed to verify hypotheses and diagnose failures.

Related Skills

Explore More Software Engineering Skills→
gaebalaigaebalai
2

bug-triage

Analyze error logs and Git history to generate bug hypotheses and troubleshooting plans.

Community
Intermediate
yocxy2yocxy2

ios-clean

Remove DebugBridge SPM packages and conditional debug instrumentation from iOS project files.

Community
Intermediate
rajveersingh11rajveersingh11

ci-triage

Classify CI failures into flake, regression, environment, or configuration issues.

Community
Basic
LuminairPrimeLuminairPrime
1

investigate

Investigate software bugs through root-cause analysis and hypothesis testing.

Community
Advanced