What problem does it solve? Teams that vendor custom Oxlint lint rules need a repeatable way to install, configure, and later update those rules without clobbering local edits, losing provenance, or breaking dependency versions. This Skill guides a safe fresh install and a reviewed three-way merge for updates. ## Core Features & Use Cases - Fresh installation: Copies the bundled anti-slop plugin into the target repository, pins matching oxlint and @oxlint/plugins versions, and registers all generic rules plus the opt-in Effect plugin in Oxlint or Vite+ configuration. - Vendored updates: Performs a three-way merge (local, incoming, base) that preserves local rule customizations, disabled rules, and configuration policy instead of replacing the directory. - Provenance tracking: Records source identity, adopted changes, and intentional deviations in UPSTREAM.md beside the vendored entry point. - Use Case: A repository already vendors anti-slop with locally tuned rules; when upstream fixes arrive, use this Skill to stage the incoming snapshot, merge only reviewed changes, run lint and typecheck, and record exactly what was adopted. ## Quick Start Ask the agent to install the anti-slop Oxlint plugin into this repository and configure all its rules, or to update the existing vendored anti-slop installation while keeping my local customizations.
