symfony-sk:error-code

Generate standardized error codes with FR/EN translations for Symfony migrations.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Swoking/symfony-sk-plugin --skill symfony-sk-error-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: symfony-sk:error-code
Source: https://github.com/Swoking/symfony-sk-plugin/tree/main/plugins/symfony-sk/skills/error-code
Command: npx skills add https://github.com/Swoking/symfony-sk-plugin --skill symfony-sk-error-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and management of standardized return codes for Symfony migrations, including translations, to ensure consistent error handling across forms and services.

Core Features & Use Cases

  • Generate standardized codes using the -XXYZZ convention and attach FR/EN translations.
  • Validate and cache codes to avoid duplicates and streamline migrations.
  • Integrate with migrations to apply new codes alongside error handling.

Quick Start

Propose a new error code and generate translations for FR and EN for inclusion in the next migration.

Frequently Asked Questions about symfony-sk:error-code

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

FAQPage Schema
How do I standardize error codes in Symfony migrations?

Standardize error codes in Symfony migrations by applying a -XXYZZ naming convention to form validation and service errors, attaching FR/EN translations, and caching codes to prevent duplicates. A confirmation step occurs before writing.

Can I add multilingual translations to Symfony form validation errors during migrations?

Yes, you can add multilingual translations to Symfony form validation errors during migrations. The process attaches FR and EN translations directly to standardized error codes, ensuring consistent multilingual support across services.

What is the -XXYZZ naming convention for backend error codes?

The -XXYZZ naming convention is a structured format used to generate standardized backend error codes for Symfony migrations. It ensures consistent error handling and easy lookup across forms and services while preventing duplicates.

How do I avoid duplicate error codes when running Symfony migrations?

Avoid duplicate error codes in Symfony migrations by validating and caching codes in a repository before writing. The system checks existing codes against the cache to streamline migrations and maintain consistent error handling.

Does this approach require a confirmation step before applying migration error codes?

Yes, applying migration error codes requires a user confirmation step before writing. This ensures the proposed standardized codes and their FR/EN translations are reviewed and validated before integration into the migration workflow.