error-reporter

Consolidate execution-time error information into a structured error-report artifact.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Burburton/amazing-specialists --skill error-reporter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-reporter
Source: https://github.com/Burburton/amazing-specialists/tree/main/.opencode/skills/common/error-reporter
Command: npx skills add https://github.com/Burburton/amazing-specialists --skill error-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts scattered error information from execution into a single, standard error-report artifact, enabling rapid diagnosis and decision-making by management and engineers.

Core Features & Use Cases

  • Classifies errors into a consistent taxonomy, mapping to severity and recommended actions.
  • Generates traceable error reports with source references to artifacts, files, and logs.
  • Integrates with failure-analysis outputs to produce a complete, ready-to-consume artifact for execution-reporting.

Quick Start

Run the error-reporter after failure-analysis completes to produce a standardized error-report artifact.

Frequently Asked Questions about error-reporter

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

FAQPage Schema
How do I standardize execution-time errors into a structured report?

To standardize execution-time errors into a structured report, consolidate scattered error_context and error_description data into a single artifact. This process applies a consistent taxonomy to classify errors and map them to severity levels for rapid diagnosis.

What is error taxonomy and how does it support incident remediation?

Error taxonomy is a classification system that categorizes execution failures into consistent severity levels and recommended actions. It supports incident remediation by providing traceable source references to artifacts, files, and logs for reliable governance.

Can I use failure-analysis outputs to generate actionable error reports?

Yes, you can use optional failure_analysis_output inputs to generate actionable error reports. Integrating failure-analysis outputs during the preparation, execution, and verification phases produces a complete, ready-to-consume artifact for execution-reporting.

How do I add traceability to scattered error logs and execution artifacts?

Add traceability to error logs by consolidating execution-time error information into a standard artifact with source references. This generates traceable outputs linking errors directly back to specific files, logs, and artifacts for decision-making.

Does this error-reporting approach work across preparation, execution, and verification phases?

Yes, this error-reporting approach works across preparation, execution, and verification phases. It leverages error_context and error_description inputs throughout these phases to consistently evaluate severity and classify failures into a standardized taxonomy.