DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to fix mechanical PHP findings in one pass with Sloppy

Let Rector and Pint fix the findings a machine can change, then review what is left.

Who it is forA PHP developer with a backlog of Sloppy findings who wants the mechanical ones cleared quickly.

The problemMechanical findings such as restating comments take time to fix by hand, while judgement-based findings still need a person.

The outcomeMechanical findings are fixed, formatting is applied, and a list of findings that still need a person remains.

What you need first

  • PHP 8.3 or newer
  • Composer
  • A PHP project with source roots listed in composer.json
  • Git, for diff and review commands

Steps

  1. Commit or stash current work so the changes from the fix pass are easy to review.
  2. Run vendor/bin/sloppy to list the findings before fixing.
  3. Run vendor/bin/sloppy fix to apply Rector, remove narrating comments and format with Pint. (inferred, check the README)
  4. Run vendor/bin/sloppy again and review the remaining findings that need a person.

Prompt for your agent

In the Heyosseus/sloppy project, run the fix command on the PHP repository at <project path>. Output the number of findings before and after the fix pass, and the findings that still need a person. Verify that the test suite of the project still passes after the fix.

Caveat. The fix pass changes code with Rector and Pint, so the project's own tests should be run after it, as the README does not promise the output is behaviour-preserving for every project.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page