docs: add cross-reference to cpp-linter-hooks

[shenxianpeng]

Add a TIP callout in the README recommending cpp-linter-hooks for users who prefer pre-commit hooks over GitHub Actions, with bidirectional cross-linking between the two projects.

Summary by CodeRabbit

• Documentation
  • Added a new tip in the README recommending users explore the cpp-linter-hooks pre-commit hook repository as an alternative to GitHub Actions. This option provides consistent C++ linting with clang-format and clang-tidy without requiring manual LLVM installation, delivering a simplified setup experience. Users can now make an informed choice based on their workflow needs.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 23a2b330-ca1f-4944-adc2-a4d1d63d1290

📥 Commits

Reviewing files that changed from the base of the PR and between 9a513b1 and f6d026f.

📒 Files selected for processing (1)

• README.md

---

Walkthrough

This pull request adds a callout tip to the README recommending users prefer the cpp-linter-hooks pre-commit hook repository over the GitHub Action, highlighting its ability to run clang-format and clang-tidy consistently without requiring manual LLVM installation.

Changes

Documentation Enhancement

Layer / File(s)	Summary
README TIP callout for cpp-linter-hooks README.md	A Markdown TIP callout is added near the introduction, recommending the cpp-linter-hooks pre-commit hook repository as an alternative to the GitHub Action, with a link and brief description of its benefits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• 2bndy5

🚥 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: adding a cross-reference to the cpp-linter-hooks repository in the documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/add-cross-reference-to-hooks

---

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 and usage tips.}

[2bndy5]

In case your interested, there's a markdown linter pre-commit hook written in rust: rumdl-pre-commit. It works with the config files supported by the original MarkDownLinter (written in JS).

Lately, I've been using deno's builtin markdown formatter, which seems to satisfy most MD linters' rules. And there's a rumdl VSCode extension too.

[shenxianpeng]

I’m fine with having Markdown linting or not; most of the time it’s easy enough to get Markdown formatting right.

Besides the Rust project mentioned above, I also came across another Rust project: lychee (https://github.com/lycheeverse/lychee).

[2bndy5]

I've also been secretly switching to prek instead of pre-commit. It works much faster, but its not great for python projects where the mypy is used as a pre-commit hook.