Feature Request: init to take optional --lang and --framework parameters

[cleder]

🚀 Feature Request: init command with optional --lang and --framework parameters

Summary

It is requested that the prek initialization command (init) be extended to accept optional --lang (language) and --framework parameters. This would allow the tool to automatically scaffold a more relevant and production-ready initial configuration file (.pre-commit-config.yaml) based on the project's primary technology stack.

Motivation

Many languages and frameworks have popular, community-standard custom linters, formatters, and code quality tools (e.g., black for Python, eslint for JavaScript/React, go fmt for Go).

Currently, setting up a new project requires the user to manually:

1. Identify the recommended quality tools for their stack.
2. Look up the corresponding pre-commit hook repository URLs, revisions, and arguments.
3. Manually edit the .pre-commit-config.yaml file.

Implementing the --lang/--framework parameters would drastically simplify onboarding, encourage the adoption of best practices, and reduce boilerplate, allowing developers to set up a comprehensive quality gate with a single command.

Proposed Command Examples

# Initialize with standard Python hooks (e.g., black, flake8/ruff, isort)
pre-commit init --lang=python

# Initialize with JavaScript hooks, including React-specific linters (e.g., eslint + react-hooks plugin)
pre-commit init --lang=javascript --framework=react

# Initialize for a simple Go project (e.g., go fmt, go vet)
pre-commit init --lang go

# rust with bevy game engine (cargo fmt, clippy, bevy cli)
pre-commit init --lang=rust --framework=bevy

This will be of course a very OPINIONATED choice, but we can iterate on it over time ;-)

[cleder]

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).

It is one of the favourite tools in my toolbox. ❤️

Whenever I create a new repo, I have 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.

Sorry (🍷) this is a bit of AI slop, I am using a lot of rust tooling currently where the init command is quite common and did not remember prek sample-config (🍷 again), so I asked an LLM to flesh my idea out for me.

IMHO, such an init command would be a nice addition.