[docs] chore: add CodeRabbit PR badge

[Wangmerlyn]

Summary by CodeRabbit

• Chores
  • Updated README to add a CodeRabbit Pull Request Reviews badge. Documentation-only update; no functional or behavioral changes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Added a CodeRabbit Pull Request Reviews badge line to README.md; documentation-only change with no functional, logic, or control-flow modifications.

Changes

Cohort / File(s)	Summary
Documentation Badge README.md	Added CodeRabbit Pull Request Reviews badge image line to README.md (documentation-only)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰✨ A tiny badge hops into view,
Nestled in README, shiny and new,
I nibble a carrot, then give a cheer,
Reviews are brighter with CodeRabbit here! 🥕🎖️

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a CodeRabbit PR badge to the documentation (README.md).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/coderabbit-badge

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4481630 and 612aa40.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

README.md

[uncategorized] ~7-~7: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ps://img.shields.io/coderabbit/prs/github/Wangmerlyn/KeepGPU)](https://coderabbit.a...

(COMMA_COMPOUND_SENTENCE_2)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Build documentation
• GitHub Check: Run pre-commit checks
• GitHub Check: build

🔇 Additional comments (1)

README.md (1)

7-7: Excellent – the badge suggestion from the prior review has been addressed!

The CodeRabbit badge is properly implemented as a clickable link, consistent with the other badges in the file (PyPI, Docs, DOI, DeepWiki). The markdown syntax is correct, and the badge will route users to the CodeRabbit dashboard as intended.

Note: The static analysis hint about comma usage is a false positive—markdown link syntax does not follow sentence-level punctuation rules and should be ignored.

---

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

[gemini-code-assist]

Summary of Changes

Hello @Wangmerlyn, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the project's documentation by integrating a CodeRabbit PR badge into the README.md. This addition provides a visual indicator of the pull request review status, offering a quick overview of development activity for contributors and visitors.

Highlights

• Documentation Update: Added a CodeRabbit PR badge to the README.md file.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a CodeRabbit badge to the README.md file, which is a nice touch for project transparency. I've provided one suggestion to make the badge a clickable link, aligning it with the style of other badges in the file and improving usability for visitors.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

9-9: Minor grammar note (pre-existing).

The static analysis tool flagged a compound sentence structure on line 9. The phrase "It allocates just enough VRAM and issues lightweight CUDA work so schedulers observe..." would benefit from a comma before 'so' to separate independent clauses. This is a pre-existing issue unrelated to the badge addition, but worth fixing in a future pass.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 54d2b14 and 4481630.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

README.md

[uncategorized] ~7-~7: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...s://img.shields.io/coderabbit/prs/github/Wangmerlyn/KeepGPU) Keep GPU keeps sh...

(COMMA_COMPOUND_SENTENCE_2)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Build documentation
• GitHub Check: build
• GitHub Check: Run pre-commit checks

🔇 Additional comments (1)

README.md (1)

7-7: LGTM! Badge addition looks good.

The CodeRabbit badge is properly formatted, correctly referenced, and well-placed alongside the other badges at the top of the README. The markdown syntax and badge URL follow the established pattern from the other shields.io badges.