Skip to content
TrustedSkillsbeta
Back to all skills

Laravel:Controller Cleanup

Checked
jpcaparas·vlatest·backend·MIT

This skill automatically cleans up unused code and outdated configurations within Laravel controllers, boosting project maintainability and efficiency.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jpcaparas/superpowers-laravel --skill laravel:controller-cleanup -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jpcaparas

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jpcaparas/superpowers-laravel at c5198b16cd.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c5198b16cd
Manifest
skills/controller-cleanup/SKILL.md
Scanned
1 file, 36 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automatically cleans up unused controllers in a Laravel project. It identifies and removes controller files that are not referenced within routes, middleware, or other controllers, streamlining the codebase and reducing unnecessary bloat. The cleanup process ensures only actively used controllers remain, improving maintainability and development efficiency.

When to use it

  • After refactoring a large Laravel application where some controllers might have been deprecated or removed manually.
  • During code reviews to ensure that no unused controller files are present in the project.
  • As part of an automated build process to keep the codebase clean and organized.
  • When preparing a Laravel project for deployment, ensuring only necessary components are included.

Key capabilities

  • Identifies unused controllers within a Laravel project.
  • Removes identified controller files from the file system.
  • Provides a list of removed controllers for review.

Example prompts

  • "Clean up any unused controllers in my Laravel application."
  • "Find and remove controllers that are not used in routes or middleware."
  • "Run the controller cleanup process and show me which files were deleted."

Tips & gotchas

This skill requires a working Laravel project to be active. Be sure to back up your project before running this skill, as it permanently removes files.