chore: update the pre-commit hooks quarterly

[shenxianpeng]

pre-commit.ci checks for new hook versions every week by default and
opens a pull request whenever there is one, and each needs a review.
Once a quarter is enough for linters and formatters, and it is what
cpp-linter/cpp-linter already does. A hook can still be updated by hand
with pre-commit autoupdate when needed.

This repository had no ci settings, so it also gets the ones the
other repositories use, which give pre-commit.ci's pull requests and
commits conventional titles.

Summary by CodeRabbit

• Chores
  • Added settings for automated code-fix pull requests and scheduled quarterly update checks, with consistent commit messages. These maintenance changes support repository upkeep and do not change product features or the experience available to end users.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: b31d4646-d7fa-4f8a-9470-d06e89a7c5da

📥 Commits

Reviewing files that changed from the base of the PR and between 2f0561f and 6316f33.

📒 Files selected for processing (1)

• .pre-commit-config.yaml

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

Walkthrough

The pre-commit configuration enables autofix pull requests, sets autofix and autoupdate commit messages, and schedules autoupdates quarterly.

Changes

Pre-commit Automation

Layer / File(s)	Summary
Configure autofix and autoupdates .pre-commit-config.yaml	The configuration enables autofix pull requests, sets commit messages for autofix and autoupdate, and schedules quarterly autoupdates.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~4 minutes

Merge Risk: ⚪ Minimal · up to 6316f

Autofix pull requests and quarterly hook updates use supported pre-commit.ci settings; no user-facing or production behavior change presents an actionable merge risk.

Architecture Summary

Architecture risk: 🔵 Low · up to 6316f

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .pre-commit-config.yaml: Adds pre-commit automation settings: enables autofix PRs, sets commit messages for autofix and autoupdate, and schedules autoupdates quarterly.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: changing pre-commit hook updates to a quarterly schedule.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}