skills.rest
pprice
ppriceCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

adding-error-codes

Add diagnostic error codes to the Vole compiler with snapshot testing.

3|Updated Jan 2, 2026
Search Tags:#testing#developer tools#debugging#error codes#compiler#vole
One-click install
npx skills add https://github.com/pprice/vole --skill adding-error-codes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adding-error-codes
Source: https://github.com/pprice/vole/tree/main/.claude/skills/adding-error-codes
Command: npx skills add https://github.com/pprice/vole --skill adding-error-codes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of adding new diagnostic error codes to the Vole compiler, ensuring consistency and proper tracking of development issues.

Core Features & Use Cases

  • Error Code Generation: Automatically finds the next available error code in the sequence for lexer, parser, or semantic errors.
  • Error Emission Guidance: Provides clear instructions on where to add new error variants and how to emit them in the compiler's codebase.
  • Testing Integration: Guides the user through adding snapshot tests to verify error messages and ensures code quality with pre-commit checks.
  • Use Case: A developer needs to introduce a new semantic error for a recently implemented language feature. This Skill will help them find the correct error code, implement the error reporting, and add a test case.

Quick Start

Use the adding-error-codes skill to get the next available semantic error code.

Frequently Asked Questions about adding-error-codes

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

FAQPage Schema
How do I add new compiler error codes to the Vole compiler?▼

Vole compiler error codes follow a structured convention: E0xxx for lexer errors, E1xxx for parser errors, and E2xxx for semantic errors. This categorization ensures consistent tracking and organization of diagnostic issues across the compilation pipeline.

What's the best way to find the next available error code for a semantic error?▼

Yes, testing new compiler error codes requires adding snapshot tests to verify the emitted error messages. This ensures code quality and validates that the diagnostic output matches expectations before committing changes to the Vole compiler repository.

Can I use this workflow for lexer and parser errors as well as semantic errors?▼

Vole compiler error codes follow a structured convention: E0xxx for lexer errors, E1xxx for parser errors, and E2xxx for semantic errors. This categorization ensures consistent tracking and organization of diagnostic issues across the compilation pipeline.

What's the best way to find the next available error code for a semantic error?▼

Yes, testing new compiler error codes requires adding snapshot tests to verify the emitted error messages. This ensures code quality and validates that the diagnostic output matches expectations before committing changes to the Vole compiler repository.

Related Skills

Explore More Software Engineering Skills→
c-tomiokac-tomioka

moonbit-investigating-errors

Diagnose MoonBit compiler errors and generate prioritized fix plans.

Community
Advanced
jrmatherlyjrmatherly
1

precheck

Run backend tests, lint, and frontend type checks before commits.

Community
Intermediate
JonathanMitchell1234JonathanMitchell1234

pcl-expert

Explain Persona Control Language syntax, compiler phases, and runtime systems.

Community
Advanced
sakamoto-family-smilesakamoto-family-smile

google-workspace-ops

Coordinate edits across Google Docs, Sheets, and Slides from Drive.

Community
Advanced