update-precommit

To automatically update pre-commit hooks, the Skill reads .pre-commit-config.yaml, queries GitHub for the latest release tag of each repo, and updates the rev entries. This keeps hook versions current across local and CI environments without manual editing.

Bump pre-commit hook rev versions by querying the GitHub API for the latest release tag for each configured repository and updating the .pre-commit-config.yaml file. The process preserves the original rev formatting, including existing quotes and version prefixes.

Yes, updating .pre-commit-config.yaml preserves the original rev formatting. The Skill maintains the existing quotes and v-prefixes while applying the latest release tags, ensuring your configuration syntax remains intact and valid across environments.

Yes, you can use this to keep pre-commit configurations consistent across CI pipelines. By bumping all repo rev entries to the latest GitHub release tags, the Skill ensures that hook versions remain synchronized and current across both local development and CI environments.

The best way to update multiple pre-commit repositories at once is to run a Skill that reads .pre-commit-config.yaml, queries the GitHub API for each repo's latest release tag, and applies the updates to the file simultaneously, avoiding manual repository-by-repository editing.

No, you do not need to manually specify the latest release tag for each pre-commit hook. The Skill automatically queries the GitHub API to find the latest release tag for every repository listed in .pre-commit-config.yaml and applies the discovered versions directly.