install-anti-slop
Skill1.4k starsChanged 5 days agoMITView on GitHub
Install, configure, update, or upgrade vendored anti-slop Oxlint plugins. Use when adding anti-slop, picking up upstream rules or fixes, or migrating an existing installation while preserving local customizations.
8 other projects use a version of this, 5 of them edited; 3 of 5 edited versions we compared changed its rules; 3 new projects in the last 4 weeks, against 0 the 4 before.
How people change it
3 of 5 edited versions changed its rules, and some changes recur.
Of the 5 edited versions we compared: 2 keep every rule, 3 made changes of their own.
Rules people drop
- Read the repository's agent instructions and
git status. Identify its package manager, Oxlint/Vite+ configuration, and any existing anti-slop entry points, including renamed or relocated copies referenced byjsPlugins.dropped by 3 of 3 - No installation — fresh install: follow the procedure below. If the user requested an update but no installation can be found, confirm the target before installing.dropped by 3 of 3
- If the repository already depends on
oxlint, read its installed version from the package manager or lockfile and install@oxlint/pluginsat exactly that version. Pin it exactly rather than by range so future upgrades move both packages together.dropped by 3 of 3 - Only when the repository has no
oxlintdependency, querynpm view oxlint versionandnpm view @oxlint/plugins version, then install the same current version of both packages.dropped by 3 of 3 - If the repository declares
effectin a package manifest, or the user explicitly requests Effect rules, also register the opt-in Effect plugin:dropped by 1 of 3
Rules people add
- Read its agent instructions.added by 3 of 3
- Check
git statusand preserve unrelated changes.added by 3 of 3 - Check whether anti-slop files or rules already exist. Do not overwrite them without reviewing the diff.added by 3 of 3
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Surging: 3 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- imMamdouhaboammar/anti-slop-engineeringedited, first seen Nov 16, 2026
- Amronos/skillsword for word, first seen Nov 15, 2026
- mohammadchehab/isnadibotedited, first seen Nov 15, 2026
- dmmulroy/anti-slopword for word, first seen Oct 25, 2026
- trycompai/crmedited, first seen Oct 8, 2026
- Verbiflow/makoedited, first seen Oct 8, 2026
Who's talking about bbplayer-app/BBPlayer
- c1201y/ClassSoftwareHub“[待审核] BBPlayer (bbplayer)”GitHub · Oct 11, 2026
- oldsento/bilibili-client-software-collection“BBPlayer & bilisound 算吗”GitHub · Oct 3, 2026
- lovegaoshi/react-native-track-player“[FR] Caching”GitHub · Mar 9, 2026
The biggest 3 of 3 mentions linking to the repository that our crawl found. Each line is their own headline.
Other versions8 projects use a version of this.
Word for word · 2
- dmmulroy/anti-slop★ 5.7k100% same
- Amronos/skills★ 1100% same
Edited · 5
- trycompai/crm★ 12k43% same
- kartikkabadi/synara-beta★ 664% same
- Verbiflow/mako★ 564% same
- imMamdouhaboammar/anti-slop-engineering★ 496% same
- mohammadchehab/isnadibot★ 291% same
Wrote their own version · 1
- kuker24/OpenCodeBestFriend★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- argent-android-emulator-setupSkill
- argent-create-flowSkill
- argent-device-interactSkill
- argent-ios-device-interactSkill
- argent-ios-device-setupSkill
- argent-ios-simulator-setupSkill
- argent-lensSkill
- argent-metro-debuggerSkill
- argent-native-profilerSkill
- argent-qa-flowsSkill
- argent-react-native-app-workflowSkill
- argent-react-native-optimizationSkill
- argent-react-native-profilerSkill
- argent-screen-recordingSkill
- argent-screenshot-diffSkill
- argent-settings-permissionsSkill
- argent-test-ui-flowSkill
- argent-tv-interactSkill
- expo-moduleSkill
- Expo UI Jetpack ComposeSkill
- Expo UI SwiftUISkill
- react-doctorSkill
- react-native-ease-refactorSkill
- upgrading-expoSkill
The file
We split this skill into the rules it gives an agent
6 rules. 1 is common, 1 is distinctive, and 4 are very specific to this project.
1
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read the repository's agent instructions and git status.
- Distinctive: line 15
No installation — fresh install: follow the procedure below.
- Very specific: line 34
If the repository already depends on oxlint, read its installed version from the package manager or lockfile and install @oxlint/plugins at …
- Very specific: line 35
Only when the repository has no oxlint dependency, query npm view oxlint version and npm view @oxlint/plugins version, then install the …
- Common: line 37
Do not replace the package manager or rewrite unrelated dependency ranges.
- Very specific: line 97
If the repository declares effect in a package manifest, or the user explicitly requests Effect rules, also register the opt-in Effect …
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Install or update anti-slop
Anti-slop is vendored code: the target repository owns its rules, diagnostics, tests, and configuration. Preserve those choices when bringing in upstream changes.
Choose the path
Read the repository's agent instructions and git status. Identify its package manager, Oxlint/Vite+ configuration, and any existing anti-slop entry points, including renamed or relocated copies referenced by jsPlugins.
- Existing installation — update, upgrade, migrate, or reconfigure: read Update a vendored installation and follow that procedure instead of the fresh-install steps below.
- No installation — fresh install: follow the procedure below. If the user requested an update but no installation can be found, confirm the target before installing.
Complete when the operation and target path are established and pre-existing work is identified.
Fresh install
Copy the bundled plugin from this skill. Run from the target repository:
node <skill-directory>/scripts/install.mjsThis creates
tools/oxlint/anti-slop/. Pass another relative destination as the first argument when the repository has an established tooling layout. The script refuses to replace an existing destination; route existing copies through the update procedure rather than--force.Preserve the nested
vendor/eslint-stylistic/LICENSEandUPSTREAM.md; they travel with the copied rule. Readability enforcement is self-contained and requires no Stylistic plugin dependency.Complete when the files, including vendored license and provenance, exist at the agreed destination without replacing an existing copy.
Install current compatible dependencies rather than trusting versions remembered by the agent:
- If the repository already depends on
oxlint, read its installed version from the package manager or lockfile and install@oxlint/pluginsat exactly that version. Pin it exactly rather than by range so future upgrades move both packages together. - Only when the repository has no
oxlintdependency, querynpm view oxlint versionandnpm view @oxlint/plugins version, then install the same current version of both packages. oxlintis a development dependency. The copied source imports@oxlint/plugins, so install it as a development dependency for a local-only plugin.- Do not replace the package manager or rewrite unrelated dependency ranges.
Complete when matching compatible versions are installed and unrelated dependency ranges are preserved.
- If the repository already depends on
Register the generic plugin, configure ignores, and enable all generic rules. For
oxlint.config.tsor.oxlintrc.json, merge these fields with the existing configuration:ignorePatterns: [ ".agent/**", ".agents/**", ".claude/**", ".codex/**", ".continue/**", ".cursor/**", ".gemini/**", ".opencode/**", ".pi/**", ".roo/**", ".windsurf/**", "tools/oxlint/anti-slop/**", ], jsPlugins: [ { name: "anti-slop", specifier: "./tools/oxlint/anti-slop/index.ts" }, ],Keep every existing ignore. Adjust the final pattern when the plugin was copied elsewhere. Inspect the repository for other project-local agent tooling directories and add them rather than linting installed skills, hooks, or generated agent configuration as application source. Do not broadly ignore all dot-directories, because some repositories keep owned source or checks in them.
For Vite+, add these fields to
lint.ignorePatternsandlint.jsPlugins. Also merge the same patterns intofmt.ignorePatternssovp checkdoes not reformat installed agent assets or the vendored plugin. Merge existing entries instead of replacing them.Enable these rules at
"error", including the native Oxlint companion rule:{ "oxc/no-accumulating-spread": "error", "anti-slop/no-array-filter-map": "error", "anti-slop/no-reduce-accumulator-copy": "error", "anti-slop/no-chained-type-assertions": "error", "anti-slop/no-conditional-empty-object-spread": "error", "anti-slop/no-known-value-widening": "error", "anti-slop/no-module-mocking": "error", "anti-slop/no-object-parameters": "error", "anti-slop/no-reflect-apply": "error", "anti-slop/no-reflect-get": "error", "anti-slop/no-runtime-typeof": "error", "anti-slop/no-shape-in-symbol-names": "error", "anti-slop/no-unknown-parameters": "error", "anti-slop/no-unknown-returns": "error", "anti-slop/no-unknown-type-aliases": "error", "anti-slop/no-unsafe-dictionary-type": "error", "anti-slop/no-widen-then-assert": "error", "anti-slop/require-readable-spacing": "error", "anti-slop/require-safety-comment-for-type-assertion": "error" }For
no-array-filter-map, prefer lazy.values().filter(...).map(...).toArray()pipelines only when the target runtime supports iterator helpers; otherwise use an appropriate singleflatMapor locally mutating reducer. Review callback order, indexes, sparse arrays,thisArg, and filtering semantics rather than mechanically rewriting chains. Unknown receiver types are deliberately not inferred by this AST/scope rule.Pair
no-reduce-accumulator-copywith nativeoxc/no-accumulating-spread: the custom rule catches supported non-spread copies such asObject.assign({}, acc, item),Array.from(acc), and array accumulatorconcat/slicecalls. Mutating a fresh local accumulator is allowed; copying individual input items is also allowed. Named callbacks, indirect helpers, and nested accumulator properties are not fully analyzed, so do not claim all quadratic reducers are ruled out.If the repository declares
effectin a package manifest, or the user explicitly requests Effect rules, also register the opt-in Effect plugin:jsPlugins: [ { name: "anti-slop-effect", specifier: "./tools/oxlint/anti-slop/effect/index.ts", }, ], rules: { "anti-slop-effect/no-manual-effect-error-tag": "error", "anti-slop-effect/no-manual-tag-comparison": "error", "anti-slop-effect/no-manual-tagged-construction": "error", "anti-slop-effect/no-service-constructor-imports": "error", "anti-slop-effect/prefer-effect-match": "error", },Merge these entries with the generic plugin configuration rather than replacing it. Do not enable the Effect plugin merely because Effect appears transitively in a lockfile; require a direct package-manifest dependency or an explicit user request. The rule covers relative project imports. Report package-alias imports as a current limitation rather than pretending they are enforced.
Complete when the generic rules and eligible Effect rules are registered and existing configuration is preserved.
Run the repository's lint command and typecheck. For Vite+, run the repository's full
vp checkcommand after adding both lint and format ignores. If findings appear in owned project source, report them and fix them only when the user asked for migration/cleanup. Do not suppress rules, weaken rule severity, add unsafe casts, or mechanically launder types to make lint pass.When cleanup is authorized, apply
require-readable-spacingwith lint autofix, then run the repository's formatter and lint again. Confirm a second fix/format pass leaves files unchanged. Keep whitespace fixes separate from semantic edits, preserve documentation attachment and overload groups, and do not enable an entire competing formatting preset.Complete when checks have run, fix/format stability has been verified for authorized cleanup, and every failure is resolved or reported with its diagnostics.
Record provenance in
UPSTREAM.mdbeside the vendored entry point: source repository, exact source commit or recoverable pristine snapshot when available, installed plugin paths, and intentional deviations. Verify that the revision identifies the actual copied assets; a package version or the current upstream HEAD alone is insufficient. If provenance cannot be established, record it as unknown rather than guessing.Review the final diff and report the installed path, source identity, dependency/configuration changes, and check results. Complete when the record and report describe the files actually installed and any remaining findings.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

