castor

Discover and execute Castor lifecycle tasks for containerized Symfony projects.

2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ineersa/symfony-web-template --skill castor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: castor
Source: https://github.com/ineersa/symfony-web-template/tree/main/.agents/skills/castor
Command: npx skills add https://github.com/ineersa/symfony-web-template --skill castor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes discovery and execution of project maintenance and lifecycle tasks so developers avoid running ad hoc Docker commands, host PHP binaries, or scattered scripts when working with a Symfony project.

Core Features & Use Cases

  • Task discovery: Use castor list, castor list dev, or castor list prod to enumerate available tasks and namespaces.
  • Unified lifecycle commands: Run local development, production-like compose, migrations, tests, and Composer/Symfony console commands through a consistent task runner.
  • Developer workflow hygiene: Prefer castor tasks over manual docker compose or host PHP usage to ensure reproducible, container-aware executions.

Quick Start

Start the local development environment and list available tasks by running castor dev:up and then castor list.

Frequently Asked Questions about castor

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

FAQPage Schema
How do I automate Docker lifecycle tasks for a Symfony project?

You can automate Docker lifecycle tasks for a Symfony project by defining them in a castor.php configuration file and executing commands like dev:up or prod:up. This replaces manual Docker commands with reproducible, container-aware executions.

What is the best way to run Symfony console commands inside Docker containers?

The best way to run Symfony console commands inside Docker containers is using a task runner like Castor. It executes console operations deterministically within your containerized environment, avoiding host PHP binaries or scattered scripts.

Do I need a specific Docker compose file structure to use Castor for prod:up?

Yes, you need a valid compose.prod.yaml file to use Castor for prod:up. The task runner requires appropriate compose files to match the target environment, ensuring deterministic execution of production workflows.

How do I list available dev and prod tasks in a Symfony repository?

You can list available dev and prod tasks in a Symfony repository by running castor list, castor list dev, or castor list prod. This enumerates all configured namespaces and lifecycle tasks defined in your castor.php.

Can I run database migrations and Composer operations without host PHP using a task runner?

Yes, you can run database migrations and Composer operations without host PHP by executing them through Castor tasks. This ensures all PHP operations run container-aware inside Docker, maintaining developer workflow hygiene and reproducibility.

Why should I prefer Castor tasks over manual docker compose commands?

You should prefer Castor tasks over manual docker compose commands to ensure reproducible, container-aware executions. Centralizing project maintenance and lifecycle tasks avoids scattered scripts, maintaining consistent developer workflow hygiene across environments.