One-click install
npx skills add https://github.com/hamzaPixl/pixl-ai --skill error-catalog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-catalog
Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/error-catalog
Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill error-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers and DevOps struggle to understand and harmonize error handling across services, leading to inconsistent messages, debugging delays, and fragile client integrations.

Core Features & Use Cases

  • Discovery and analysis of error patterns across Node.js, Python, and other backends.
  • Unified error catalog with codes, messages, and HTTP mappings.
  • Inconsistency detection across sources: missing codes, mismatched HTTP statuses, and leaking client-safe messages.
  • Optional scaffolding for standardized error infrastructure (base classes, enums, and handlers).

Quick Start

Provide the path to your service directory to scan, catalog errors, detect inconsistencies, and generate an error report.

Frequently Asked Questions about error-catalog

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

FAQPage Schema
How do I catalog service errors and standardize exception handling across my backend?

To catalog service errors, scan your backend source trees to discover thrown exceptions, error classes, and HTTP mappings. This generates a unified error catalog with codes and messages, while flagging inconsistencies like missing error codes and mismatched HTTP statuses.

What is the best way to detect inconsistent HTTP status mappings and leaking client messages in my codebase?

Detecting inconsistent HTTP status mappings and leaking client messages requires scanning your source code for error patterns. An inconsistency analysis flags these issues by auditing thrown exceptions and validation errors against your standardized error catalog.

Can I scan a specific app directory for validation errors and thrown exceptions in Node.js and Python backends?

Yes, you can scan typical source trees like app directories in Node.js and Python backends. By providing a path for optional scoping, the analysis discovers validation errors and thrown exceptions to map them into a structured catalog.

How do I generate standardized error infrastructure with base classes and enums for my API?

To generate standardized error infrastructure, the cataloging process optionally scaffolds base classes, enums, and handlers. This creates a unified error baseline, ensuring consistent error codes, messages, and HTTP mappings across your API services.

Why does my service return mismatched HTTP statuses and missing error codes for similar exceptions?

Mismatched HTTP statuses and missing error codes occur when thrown exceptions are not centrally cataloged. Scanning your source directories detects these inconsistencies by auditing your error classes and validation issues against a unified standard.

Do I need to manually map error codes to HTTP statuses before auditing my service errors?

No, you do not need to manually map error codes to HTTP statuses beforehand. The analysis discovers existing thrown exceptions and HTTP mappings automatically, identifying missing codes and generating a structured catalog with proper mappings.