Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
makfly avatar

Symfony:controller Cleanup Skill

  • 539 installs
  • 190 repo stars
  • Updated August 6, 2026
  • makfly/superpowers-symfony

symfony:controller-cleanup is an agent skill that refactors bloated Symfony controllers into focused services and actions for developers who need safe, checkpointed architectural cleanup in PHP backends.

About

symfony:controller-cleanup is an agent skill from makfly/superpowers-symfony for refining architecture, workflows, and context handling in Symfony projects through a guarded controller cleanup workflow. Listed on skills.sh with 436 installs and rank 3 in its repository, it follows a four-step default process: establish current boundaries, constraints, and coupling points; propose the smallest coherent architectural adjustment; execute in checkpoints with validation at each stage; and summarize tradeoffs plus a follow-up backlog. Guardrails require using existing project patterns by default, avoiding broad refactors without explicit need, and keeping a clear auditable decision log. Developers reach for symfony:controller-cleanup when Symfony controllers accumulate business logic, violate single-responsibility, or block testability and want incremental extraction into services rather than a risky rewrite. The skill plans and executes medium-to-complex Symfony changes safely instead of offering generic PHP advice. It assumes an existing Symfony codebase where sibling files reveal established conventions to preserve.

  • Automatically extracts business logic from fat controllers into dedicated service classes
  • Creates or updates action classes following Symfony best practices
  • Removes duplicated code and improves maintainability across your codebase
  • Works with existing Symfony projects without breaking changes
  • Reduces controller complexity that commonly accumulates during feature development

Symfony:Controller Cleanup by the numbers

  • 539 all-time installs (skills.sh)
  • Ranked #794 of 4,492 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 11, 2026 (Skillselion catalog sync)
npx skills add https://github.com/makfly/superpowers-symfony --skill symfonycontroller-cleanup

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs539
repo stars190
Last updatedAugust 6, 2026
Repositorymakfly/superpowers-symfony

How do you refactor fat Symfony controllers safely?

Automatically refactor bloated Symfony controllers into clean, focused services and actions.

Who is it for?

Symfony backend developers cleaning up overgrown controllers who want smallest-change refactors with checkpoint validation and an auditable decision log.

Skip if: Non-Symfony PHP projects or teams seeking automatic large-scale rewrites without explicit need for bounded architectural adjustments.

When should I use this skill?

Symfony controllers are bloated with business logic and the user asks to extract services, clean up actions, or improve controller architecture safely.

What you get

Extracted Symfony services, slimmer controller actions, checkpoint validation notes, and a tradeoff backlog.

  • Refactored Symfony services
  • Slimmer controller actions
  • Architectural tradeoff backlog

By the numbers

  • Listed with 436 installs and rank 3 on skills.sh
  • Defines a 4-step default controller cleanup workflow with checkpoint validation

Files

SKILL.mdMarkdownGitHub ↗

Controller Cleanup (Symfony)

Use when

  • Refining architecture/workflows/context handling in Symfony projects.
  • Planning and executing medium/complex changes safely.

Default workflow

1. Establish current boundaries, constraints, and coupling points. 2. Propose smallest coherent architectural adjustment. 3. Execute in checkpoints with validation at each stage. 4. Summarize tradeoffs and follow-up backlog.

Guardrails

  • Use existing project patterns by default.
  • Avoid broad refactors without explicit need.
  • Keep decision log clear and auditable.

Progressive disclosure

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

Output contract

  • Architecture/workflow changes.
  • Checkpoint validation outcomes.
  • Residual risks and next steps.

References

  • reference.md
  • docs/complexity-tiers.md

Related skills

FAQ

What workflow does symfony:controller-cleanup follow?

symfony:controller-cleanup uses four steps: map boundaries and coupling, propose the smallest coherent adjustment, execute with per-checkpoint validation, then summarize tradeoffs and backlog items. Broad refactors require explicit justification.

Does symfony:controller-cleanup preserve existing Symfony patterns?

symfony:controller-cleanup defaults to existing project patterns and keeps a clear decision log. Agents should avoid wide rewrites unless explicitly needed, favoring the smallest architectural change that improves controller focus.

Backend & APIsbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.