mcpField
D
daily-workflow

daily-workflow

github.com/dev-toolingsDevelopment22782 installsUpdated 3w ago
Repository

About daily-workflow

A Symfony skill for starting or resuming project work and handling routine development tasks. It sets out a test-first workflow, practical debugging steps, and checks to run before committing changes.

Key features

  1. 01Project sync and setup checks
  2. 02Small test-first work cycles
  3. 03Debugging with console and profiler
  4. 04Pre-commit quality checks
  5. 05Database and debug-code safeguards

Use cases

  1. 01Resuming work on a Symfony project
  2. 02Running migrations or consuming messages
  3. 03Debugging with logs and profiler
  4. 04Preparing a change for commit

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dev-toolings/superpowers-symfony --skill daily-workflow

After installing, type/daily-workflowin Claude Code to confirm it loaded.

Bundled filesreference.md

Details

From the project README

Daily Workflow (Symfony)

Use when

  • Starting or resuming a work session on a Symfony project.
  • Routine tasks: migrations, fixtures, consuming messages, clearing the cache.
  • Debugging with debug:* commands, the profiler, and the logs.
  • Getting a change ready to commit.

Default workflow

  1. Sync: pull, run composer install when the lock file changed, apply pending migrations.
  2. Start the services the project uses and check bin/console about.
  3. Work in small test-first cycles with the project's test runner.
  4. Debug with debug:* commands, the profiler and var/log/dev.log before adding dumps.
  5. Before committing, run style, static analysis and tests, and remove every dump() and dd().

Guardrails

  • Prefix commands with the runner the project uses (Docker or host), from the runtime context.
  • Never load fixtures or reset the schema on a shared or production database.
  • Do not commit dump(), dd() or debug-only code.
  • Do not patch vendor/ to work around a problem.

Progressive disclosure

  • Use this file for execution posture and risk controls.
  • Open references when deep implementation details are needed.

Output contract

  • The commands run, with the project's runner prefix.
  • Debugging findings, with the evidence behind them.
  • A change ready to commit, quality gates green.

References

  • reference.md

Comments

Markdown supported