smith-debug

Name: smith-debug
Availability: InStock
Author: ATTCK

Run a read-only diagnostic workflow and generate a structured debug report.

50|8|Updated Apr 12, 2026

Search Tags:#automation #logs #debug #traceability #diagnose #diagnostic-workflow

Ready to run

npx skills add https://github.com/ATTCKDigital/smith --skill smith-debug

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A diagnostic-only workflow that systematically investigates errors, failures, and unexpected behavior across Armory's services. Produces a structured debug report stored in the relevant system's .specify/ folder. Does NOT modify code — the report becomes input to /smith-bugfix if a fix is warranted.

Core Features & Use Cases

Read-only diagnostic workflow that captures symptoms, triages with sub-agents, and generates a formal report.
Logs evidence to the vault session log and records artifacts and impacted systems.
Guides users through triage, diagnosis, and decision gate to fix or close.
Supports ledger integration for post-run reflection and cross-system references.

Quick Start

Describe the issue and run /smith-debug to begin the diagnostic workflow.

Frequently Asked Questions about smith-debug

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

FAQPage Schema

How do I diagnose complex service errors without modifying the codebase?▼

You can diagnose complex service errors without modifying code by running a read-only diagnostic workflow that captures symptoms, triages findings, and generates a structured debug report for historical cross-reference.

What is a structured debug report and how does it support traceability?▼

A structured debug report consolidates symptoms, triage findings, and root-cause hypotheses into a formal file. It supports traceability by logging evidence to session logs and recording impacted systems and artifacts.

How do I start a diagnostic workflow for unexpected service behavior?▼

To start a diagnostic workflow for unexpected behavior, describe the issue and run the debug command. The workflow guides you through triage, diagnosis, and a decision gate to fix or close the investigation.

Can I use automated logging for post-run reflection and ledger integration?▼

Yes, you can use automated logging for post-run reflection because the diagnostic workflow supports ledger integration and logs evidence to the vault session log to support cross-system references.

What is the best way to document root-cause hypotheses for system failures?▼

The best way to document root-cause hypotheses for system failures is using a non-destructive investigation workflow that outputs a formal report into the relevant .specify directory, suitable for subsequent bugfix actions.

When should I avoid using a read-only diagnostic workflow?▼

You should avoid using a read-only diagnostic workflow when a code modification is immediately required, because this workflow is strictly non-destructive and only generates a report for a separate bugfix process.