deployerphp-command-authoring

Author and validate DeployerPHP Symfony Console commands and Traits.

1|Updated Feb 8, 2026

Search Tags:#tests #command-authoring #deployerphp #symfony-console #prompt-parity #early-validation

Ready to run

npx skills add https://github.com/loadinglucian/dotagents --skill deployerphp-command-authoring

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deployerphp-command-authoring
Source: https://github.com/loadinglucian/dotagents/tree/main/deployer-php/skills/deployerphp-command-authoring
Command: npx skills add https://github.com/loadinglucian/dotagents --skill deployerphp-command-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Author and modify DeployerPHP Symfony Console commands and Traits, including prompt-to-option parity, early conflict validation, validator usage, command replay behavior, and registration in SymfonyApp. Use when editing app/Console/, app/Traits/, command wiring, or command-focused tests.

Core Features & Use Cases

Prompt-to-option parity enforced for all prompts
Early validation after parent::execute() and immediate conflict checks
Reuse of standard validator usage and exception handling patterns
Command registration updates in SymfonyApp and docs synchronization after changes

Quick Start

Edit commands and traits according to the rules, then run docs-agent to synchronize documentation.

Frequently Asked Questions about deployerphp-command-authoring

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

FAQPage Schema

How do I enforce prompt-to-option parity in DeployerPHP Symfony Console commands?▼

You can enforce prompt-to-option parity by authoring Symfony Console commands and Traits that align all interactive prompts with their corresponding input options. This ensures consistent execution paths and predictable command behavior.

How do I add early conflict validation to a Symfony Console command?▼

Early conflict validation is added by performing immediate checks right after calling parent::execute() in your Symfony Console command. This catches conflicting input options before the main logic processes them, ensuring early validation and predictable behavior.

What is the best way to keep SymfonyApp command registration and documentation synchronized?▼

The best way to synchronize command registration and documentation is to update the SymfonyApp wiring after editing commands or Traits, then run a docs-agent to automatically synchronize the documentation with the latest command changes.

Why does my DeployerPHP command replay behavior fail during execution?▼

Command replay behavior fails when commands lack consistent error handling and standard validator usage. Implementing early validation after parent::execute() and reusing standard exception patterns ensures predictable replay behavior and resolves execution failures.

Do I need to update tests when modifying app/Traits for Symfony Console commands?▼

Yes, you need to update command-focused tests when modifying app/Traits or app/Console files. Tests must cover command registration in SymfonyApp and verify consistent error handling to maintain reliable command behavior.