debug

Name: debug
Availability: InStock
Author: JamSuite

Diagnose failures and generate structured debug reports under assets.

1|1|Updated Feb 25, 2025

Search Tags:#debug #engineering #diagnose #root-cause #spec-plan #debug-report

Ready to run

npx skills add https://github.com/JamSuite/jim --skill debug-jamsuite

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/JamSuite/jim/tree/main/skills/debug
Command: npx skills add https://github.com/JamSuite/jim --skill debug-jamsuite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Diagnose failures and produce a structured debug report. This is diagnosis-only and does not fix code, used when the user invokes /jim:debug, when a build fails and a root-cause analysis is needed before deciding on a fix.

Core Features & Use Cases

Structured failure diagnosis with a guided workflow from error collection to root-cause hypothesis.
Linkage to related specs/plans to surface context and origin for fixes.
Generates a printable template debug report stored under assets with an origin field for traceability.

Quick Start

Describe the failure or paste error details and run /jim:debug to generate a structured report.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I diagnose a build failure and find the root cause?▼

A structured debug report diagnoses failures by gathering error output and tracing it to relevant code and spec context. It clarifies the origin of failures without performing fixes, providing a guided workflow from error collection to root-cause hypothesis.

Can I generate a structured debug report without automatically applying code fixes?▼

Yes, this diagnosis-only workflow generates a structured debug report without applying any code fixes. It traces error output to relevant specs and plans to surface context, ensuring you decide on a fix only after the root-cause analysis is complete.

What is the best way to trace error output back to its originating spec or plan context?▼

The best way to trace error output to its originating spec or plan context is by generating a structured debug report. It links failure details directly to relevant code and plans, saving a printable template with an origin field for traceability under assets.

How do I create a traceable debug report template saved under assets?▼

You create a traceable debug report template by providing failure details to generate a structured diagnosis. The workflow produces an origin-friendly report template and saves it under assets with a topic-based filename for traceability.

When do I need a root-cause analysis report before deciding on a fix?▼

You need a root-cause analysis report before deciding on a fix when a build fails and understanding the origin is critical. This structured diagnosis clarifies the failure context from relevant specs and plans, guiding the fix decision without automatically modifying code.