Hook providers
Pain point
A flat hook list shows names without explaining ownership or purpose. Grouping checks by their upstream provider makes updates, documentation, and failure investigation easier to follow.
The configuration uses remote hook repositories. Each provider owns one or more hooks and supplies the executable environment that prek runs.
| Provider | Role in this template | Configured hooks |
|---|---|---|
| pre-commit-hooks | Generic file, portability, hygiene, and repository-safety checks | 15 |
| rumdl-pre-commit | Markdown validation | 1 |
| Commitizen | Commit-message validation | 1 |
| shellcheck-py | Shell static analysis | 1 |
Open a provider page to see its official source first, followed by the hooks selected from it, why they are present, and what to do when they fail. The committed .pre-commit-config.yaml remains the source of truth for exact revisions and options.