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

How to gate CI on new PHP debt only with Sloppy

Baseline today's findings, then fail pull requests only when a branch adds new ones.

Who it is forA tech lead adopting code quality checks on an existing Laravel or PHP codebase with years of history.

The problemA first scan returns hundreds of findings, and blocking every build on old debt stops the team from merging anything.

The outcomeExisting findings are accepted into a baseline, and pull requests get annotations only for findings the branch introduced.

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. Run composer require --dev heyosseus/sloppy in the repository.
  2. Run vendor/bin/sloppy baseline to accept the debt that already exists. (inferred, check the README)
  3. Run vendor/bin/sloppy ci locally to see what the pipeline would report. (inferred, check the README)
  4. Add the GitHub Action to the workflow with uses: heyosseus/sloppy-action@v1 and diff-branch: main.

Prompt for your agent

In the Heyosseus/sloppy project, set up a baseline for the PHP repository at <project path> by running the baseline command, then run the CI command. Output the number of accepted baseline entries and the CI result. Verify that the CI command reports no findings on the unchanged branch.

Caveat. The README says baseline entries are keyed on class and member rather than line numbers, but a team still has to commit and maintain the baseline file as the codebase changes.

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