01
It starts by itself
monthly upstream check. Runs in Claude Code routine or GitHub Actions.
- ↻ monthly upstream check
0 9 1 * *
Lint rules stay current, customizations kept.
Install the Install Anti-Slop skill and make it a habit: follow https://gethabit.dev/skills/dmmulroy/install-anti-slop.md
13K installs6K starsMIT licenceSource on GitHub ↗

Install Anti-Slop
by dmmulroy · 13K installs
The skill
The install anti-slop skill installs, updates or migrates the vendored anti-slop Oxlint plugins in a repository, enables their rules and records provenance, for teams who want stricter lint rules against sloppy code.
Only when you ask.
The habit
Lint rules stay current, customizations kept.
↻ Runs by itselfmonthly upstream check
When does it start? How does it check its work? What does it remember?
Stops after one install or update of one repository per run; findings in owned source are reported, not fixed, unless you asked for cleanup.
Read the agent instructions, git status, package manager and Oxlint or Vite+ config, and find any existing anti-slop copy referenced by jsPlugins.
Follow references/update.md for an existing copy, or run scripts/install.mjs for a fresh install into tools/oxlint/anti-slop/, and ask you to confirm the target if an update finds no copy.
Install @oxlint/plugins pinned to the installed oxlint version, or query npm view for both when oxlint is missing.
Merge the ignore patterns and jsPlugins entry into the config and enable all generic rules at error, plus Effect rules only with a direct effect dependency.
Run the repository's lint command and typecheck, or vp check for Vite+, without suppressing rules or weakening severity.
Write the source repository, exact commit, installed paths and deviations into UPSTREAM.md, or mark them unknown.
Review the final diff and report the path, source identity, config changes and check results.
It writes only in its own folder and asks you before anything goes out.
Read both lists. If the left one sounds like you, the Install Anti-Slop skill helps.
No. The skill treats the plugin as vendored code the repository owns and keeps local customizations.
Only when you asked for migration or cleanup. Otherwise it reports them with diagnostics.
Only when a package manifest declares effect directly, or when you ask for them.
Copy the prompt at the top into your agent. It installs the skill from dmmulroy/anti-slop and sets up the habit. Or run npx skills add dmmulroy/anti-slop --skill install-anti-slop.
Yes. It is published under MIT. Habit is free too.
Install the Install Anti-Slop skill and make it a habit: follow https://gethabit.dev/skills/dmmulroy/install-anti-slop.md
All dmmulroy skills →More code skills →
Works in
Made by dmmulroy, published under MIT. Habit links to the original and never changes it. Is this your skill?