Using pre-commit as a polyglot task runner: elegant or kludgy? Package maintainers: does your `Makefile` or `justfile` delegate tool calls to [pre-commit](https://pre-commit.com/) (e.g., for your `lint all` targets)? I see a lot of modern repos doing it this way now. On one hand, I can see the elegance of it—`pre-commit` has basically evolved into an execution engine that manages isolated polyglot tool environments. But it still just feels weird to me, almost like a layer violation. Maybe it's just because my mental model still views `pre-commit` strictly as a git-hook manager rather than what it has actually become. One huge benefit, I guess, of having linting and quality tools delegated this way is parity: your CI pipeline, your pre-commit hooks, and your manual `justfile` targets all run the *exact* same tools in the *exact* same way. It also solves the polyglot problem.…