extract-errors

Assign unique error codes to new React error messages.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/davidsonaguiar/pqnino --skill extract-errors-davidsonaguiar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract-errors
Source: https://github.com/davidsonaguiar/pqnino/tree/main/.claude/skills/extract-errors
Command: npx skills add https://github.com/davidsonaguiar/pqnino --skill extract-errors-davidsonaguiar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when introducing new error messages in React to ensure every error has a consistent, published error code, preventing unknown-code warnings and facilitating easier error tracking across the codebase.

Core Features & Use Cases

  • Centralizes error code definitions to prevent duplicates and drift.
  • Validates new errors against a registry and highlights missing or conflicting codes.
  • Supports audit and documentation workflows for error messages across React components.

Quick Start

Run yarn extract-errors to update or assign error codes for new messages.

Frequently Asked Questions about extract-errors

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

FAQPage Schema
How do I assign unique error codes to new React error messages?

To assign unique error codes to new React error messages, run a script like yarn extract-errors that scans your codebase, identifies new errors, and updates them against a centralized error code registry to prevent duplicates.

Why do I get unknown error code warnings in my React components?

Unknown error code warnings in React components appear when new error messages lack assigned codes. A centralized registry and lint workflow validate errors against published codes, highlighting missing or conflicting entries to resolve these warnings.

What is the best way to standardize React error codes across a codebase?

The best way to standardize React error codes is to maintain a centralized error code registry and use an automated script to scan the codebase, ensuring every error message has a consistent, published code without drift or duplicates.

Do I need a centralized error code registry to extract React errors?

Yes, a centralized error code registry is required to extract React errors properly. It validates new errors against existing codes, prevents duplicates, and supports audit and documentation workflows across all React components.

How does a lint script scan a React codebase for missing error codes?

A lint script scans a React codebase for missing error codes by comparing component error messages against a centralized registry. It highlights missing or conflicting codes and applies updates when unknown error codes appear across components.

Can I audit and document error messages across React components automatically?

You can audit and document error messages across React components by running an extraction script that validates new messages against a centralized registry, ensuring consistent error tracking and preventing unknown-code warnings throughout the codebase.