skills.rest
ribatshepo
ribatshepoCOMMUNITY
Explore all skills by this author →
GitHub

debug-diagnostics

Parse errors into structured diagnostic reports with redacted secrets and history tracking.

1|Updated Mar 3, 2026
Search Tags:#debugging#diagnostics#redaction#log-analysis#structured-report#error-classification#history-tracking
One-click install
npx skills add https://github.com/ribatshepo/Auto-Orchestrate --skill debug-diagnostics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-diagnostics
Source: https://github.com/ribatshepo/Auto-Orchestrate/tree/main/claude-code/skills/debug-diagnostics
Command: npx skills add https://github.com/ribatshepo/Auto-Orchestrate --skill debug-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Diagnoses, classifies, and documents errors encountered during debugging by producing structured diagnostic reports and a persistent error history.

Core Features & Use Cases

  • Parse and classify errors from logs and traces into a consistent taxonomy.
  • Collect category-relevant diagnostics (universal, docker-related, runtime, configuration, etc.) with redacted secrets.
  • Generate diagnostic reports and live history entries to support researchers, validators, and automation pipelines.
  • Use Case: When a crash happens, run the skill to produce a report, update history, and feed the results to downstream tools.

Quick Start

Provide a raw error message to the diagnostic classifier to generate a structured report and update the error history.

Frequently Asked Questions about debug-diagnostics

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

FAQPage Schema
How do I generate a structured diagnostic report from raw error logs?▼

Yes, you can classify runtime and configuration errors into a consistent taxonomy by providing raw error messages to the classifier. It collects category-specific diagnostics and emits a standardized report for debugging sessions.

Does this diagnostics tool redact secrets and sensitive data from crash logs?▼

Yes, the diagnostics tool enforces secret redaction when parsing inputs and collecting category-specific data. It ensures sensitive information is removed before generating structured diagnostic reports and updating the error-history log.

What is the best way to track error fix history across multiple debugging sessions?▼

Track error fix history across debugging sessions by running the skill to update a persistent error-history log. It documents classified errors and generates live history entries to support researchers and validators over time.

Can I use this for log analysis across different programming languages and environments?▼

You can use this for log analysis across different programming languages. The skill applies across debugging sessions and languages, collecting category-specific data and emitting standardized reports for downstream researchers.

How do I feed classified error diagnostics into downstream automation pipelines?▼

Feed classified error diagnostics into automation pipelines by utilizing the standardized report artifact the skill emits. It generates reproducible diagnostic outputs specifically designed for downstream researchers, validators, and automation tools.

Related Skills

Explore More Software Engineering Skills→
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced
jamesjlundinjamesjlundin
32

ci-fixer

Diagnose CI/CD pipeline failures from workflow logs and propose fixes.

Community
Advanced
htlin222htlin222
77

error-detective

Search and analyze log files and codebases for error patterns and stack traces.

Community
Intermediate
XSpoonAiXSpoonAi
17

log-triage

Analyze error logs to produce root-cause hypotheses and prioritized fix plans.

Official
Advanced