@cleder Thanks, have just created a PR to add a few more.

#precommit #python #r #markdown #codespell

RE: https://hachyderm.io/@cleder/116796446972749174

My #awesomelist for #precommit and #prek is now at 60 #awesome hooks. 🎉

Find linters, formatters, security scanners, code quality tools, and more in one place.

Contributions welcome! 🔧

Languages

docker, go, img, js, md, nb, py, ru, sh, sql, tf, toml, ts, yaml

Frameworks

bevy, django, git, k8s, react, sphinx

https://github.com/cleder/awesome-pre-commit-hooks

#Python #DevOps #OpenSource #DeveloperTools #CodeQuality

The pre-commit ecosystem is huge, but discovering good hooks can be surprisingly difficult.

I've started **Awesome Pre-commit Hooks**, a curated list of #precommit and #prek hooks organised by language and framework.

Check it out and help grow it:

https://github.com/cleder/awesome-pre-commit-hooks

#Python #OpenSource #DevTools #CodeQuality #Automation

GitHub - cleder/awesome-pre-commit-hooks: A collection of awesome pre-commit/prek hooks

A collection of awesome pre-commit/prek hooks. Contribute to cleder/awesome-pre-commit-hooks development by creating an account on GitHub.

GitHub

I use pre-commit (and now are beginning to migrate to prek) extensively in all my projects (work and hobby), and create a lot of repositories (every other month or so, enough for this to be a pain point, but not enough to have the workflow committed to my muscle memory).

Whenever I created a new repo, I had to cut and paste the .pre-commit-config.yaml into the new project, which requires remembering what other project has the most appropriate and up-to-date configuration.

Now I ditched the Copy-Paste Workflow: Scaffold Your Quality Tools with pc-init

#python #prek #precommit

https://dev.to/ldrscke/stop-copying-your-pre-commit-configyaml-241d

Stop Copying Your .pre-commit-config.yaml

Tired of hunting through old repositories to copy-paste your .pre-commit-config.yaml? I’ve built a CLI tool that automates the tedious setup of linters and formatters. Whether you’re spinning up a new Python project or a React-based app, pc-init generates a production-ready quality gate in one command—no archaeology required.

DEV Community

Not sure if this is useful to anyone other than me, but I made a TODO item linter that complains if the TODO items in your code don't have an owner and a reference to an issue so someone has a chance of addressing them in the future:

https://worktree.ca/taffer/todo-linter

Works with pre-commit: https://pre-commit.com

#todo #fixme #python #pre-commit #precommit #git

todo-linter

Ensure to-do items in your code have an owner and an issue.

Worktree

prek now supports cooldown in either user or project config:

https://github.com/j178/prek/releases/tag/v0.3.12

pre-commit closed and locked the feature request as one of many many duplicates, but I can't find any:

https://github.com/pre-commit/pre-commit/issues/3614

#PreCommit #prek #cooldown

Release 0.3.12 · j178/prek

Release Notes Released on 2026-05-05. Highlights auto_update.cooldown_days is now available in both the user-level global config (~/.config/prek/prek.toml on Linux and macOS, or $XDG_CONFIG_HOME/pr...

GitHub

To aid #developers using #AI to disclose their prompts and make the #collaboration more obvious, we maintain a simple #tool that allows developers to collect all prompts and append them to commit messages:

https://github.com/pycalendar/ai-prompt-auto-commit

Projects using #Claude_code or #GitHubCopilot can automate the commit workflow using a #precommit #hook.

#generativeAI #pycal

I wanted to talk even more about dockerizing pre-commit for security gains - so I typed up a short blog post about how to achieve this.

Please feel invited to try it out and share back results ⬇️

https://overtag.dk/v2/blog/pre-commit-in-docker/

I'd also like to hear from people who aren't worried about pre-commit vulnerabilities and why ❓

#precommit #python

Running Pre-commit in Docker

Make your "pre-commit" command run in a Docker container and reduce attack surface on your development system!

A screenshot from running a dockerized pre-commit.

And here's the whole darn alias 🥳

```
$ which pre-commit
pre-commit: aliased to docker run -v "pre-commit-cache":/home/dockeruser/.cache -v "$(pwd)":/repo:rw -e PRECOMMITALIAS="$(alias pre-commit)" -e PGID="$(id -g)" -e PUID="$(id -u)" pre-commit:python3.14
```

Instructions on building and running it are in the repo ⬇️
https://codeberg.org/benjaoming/pre-commit-docker-alias

#precommit

Was contemplating if it makes sense to have a single image for ALL pre-commit needs and alias `pre-commit` to `docker run pre-commit -v "$(pwd)":/workdir:rw`

Oh and yes, this is inspired by all the supply chain stuff. If the alternative is that each pre-commit hook becomes its own Docker image, I'm afraid it'll be too slow.

Any experiences?

(edited: docker exec isn't possible with volumes)

#precommit