Conversation
📝 WalkthroughWalkthroughAdds a new MDX blog post under Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (4)
src/content/post/2025-09-13-Code-Rabbit.mdx (4)
98-105: Percentages don’t add up; clarify “Security/Critical” is a subsetAs written, the six bullets sum to 107%. If “Security/Critical” is a subset of “Quality Improvements,” fold it into that bullet so totals equal 100%.
Apply:
- - 25% were quality improvements - - and 7% of those were security/critical findings. + - 25% were quality improvements (of which 7% were security/critical findings).
22-22: Quick copyedits (spelling/grammar/clarity)Tighten a few spots for polish and correctness.
-That was very easy and straightforward. We just had to log in to their website with our Github account and it asks you to add the repositories you wish to scan. +That was very easy and straightforward. We just had to log in to their website with our GitHub account and it asks you to add the repositories you wish to scan. -CodeRabbit is impressively thorough. It finds issues that I would have easilly overlooked. +CodeRabbit is impressively thorough. It finds issues that I would have easily overlooked. -When a new PR is opened, the bot automatically edits your description to adds what this PR is doing. +When a new PR is opened, the bot automatically edits your description to add a summary of what the PR does. -Compared to the copilot sumary, it is more relevant and accurate. See for example this PR with a staggering 8500 lines of code changed! +Compared to the Copilot summary, it is more relevant and accurate. See, for example, this PR with a staggering 8,500 lines of code changed! -Then after analyzing the code for a few minutes (don't be hasty there), it adds a second comment with a summary of its findings with Request changes. +Then, after analyzing the code for a few minutes (don't be hasty), it adds a second comment summarizing its findings with "Request changes." -The comment themsleves are very well structured, and also comes with a nice dose of humor. The small bunny at the bottom is a nice touch. +The comments themselves are well structured and also come with a nice dose of humor. The small bunny at the bottom is a nice touch. -I went through all the comments that CodeRabbit made on our PRs over the last month to get some statistics. From the get go, here are some numbers. +I went through all the comments that CodeRabbit made on our PRs over the last month to get some statistics. From the get‑go, here are some numbers. -and think "Is this really what I want?" "Did I miss something?". They are not in the blattantly wrong assumption category because they are not necessarily wrong. +and think "Is this really what I want?" "Did I miss something?" They are not in the blatantly wrong assumption category because they are not necessarily wrong. -5. **Quality Improvements**: Those issues are things that needs to be fixed. Merging a pull request without having those would lead to unwanted behaviours or bugs. +5. **Quality Improvements**: Those issues need to be fixed. Merging a pull request without having those would lead to unwanted behaviours or bugs. -<tr><td> **Faulty logic**: An oversight in the control flow validation...</td><td>**IDOR vulnerability**: User could access basket from another user.</td></tr> +<tr><td> **Faulty logic**: An oversight in the control flow validation...</td><td>**IDOR vulnerability**: A user could access a basket from another user.</td></tr>Also applies to: 50-50, 53-54, 57-57, 66-66, 73-73, 88-88, 91-91, 117-117
24-26: Use semantic, accessible centering instead of deprecatedReplace
with a semantic wrapper and improve alt text where missing. MDX + Tailwind: use a div withtext-center. Also avoid Markdown images inside HTML blocks; use<img>consistently for reliable MDX parsing.-<center> -<img src="/blog/coderabbit/cr-login.png" alt="The CodeRabbit homepage" class="w-1/2" /> -</center> +<div class="text-center"> + <img src="/blog/coderabbit/cr-login.png" alt="CodeRabbit sign-in screen" class="w-1/2 inline-block" /> +</div> -<center> - -</center> +<div class="text-center"> + <img src="/blog/coderabbit/cr-repos.png" alt="CodeRabbit GitHub app — repository selection" class="w-3/4 inline-block" /> +</div> -<center> -<img src="/blog/coderabbit/cr-loading.png" alt="The CodeRabbit homepage" class="w-1/2" /> -_This screen is shown for a few seconds... (more than it should IMHO)_ -</center> +<div class="text-center"> + <img src="/blog/coderabbit/cr-loading.png" alt="CodeRabbit loading workspace screen" class="w-1/2 inline-block" /> + <p class="text-gray-500 dark:text-slate-400 text-sm italic">This screen is shown for a few seconds... (more than it should, IMHO).</p> +</div> -<center><img src="/blog/coderabbit/cr-pr.png" alt="A PR with a CodeRabbit comment" class="w-3/4" /></center> +<div class="text-center"><img src="/blog/coderabbit/cr-pr.png" alt="A PR with a CodeRabbit comment" class="w-3/4 inline-block" /></div> -<center><img src="/blog/coderabbit/cr-request-changes-comment.png" alt="A CodeRabbit comment on a PR" class="w-1/2" /></center> +<div class="text-center"><img src="/blog/coderabbit/cr-request-changes-comment.png" alt="A CodeRabbit comment on a PR" class="w-1/2 inline-block" /></div> -<center><img src="/blog/coderabbit/cr-rates.png" alt="CodeRabbit rate limits" class="w-1/2" /></center> +<div class="text-center"><img src="/blog/coderabbit/cr-rates.png" alt="CodeRabbit rate limits" class="w-1/2 inline-block" /></div>Also applies to: 30-33, 37-41, 55-55, 64-65, 132-133
114-119: Alt text consistency for “spoofing/SQL injection” exampleThe file name suggests spoofing, while the alt mentions SQL injection. Please align the alt text with the actual example to avoid confusing screen readers.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (14)
public/blog/coderabbit/analysis.pngis excluded by!**/*.pngpublic/blog/coderabbit/cr-loading.pngis excluded by!**/*.pngpublic/blog/coderabbit/cr-login.pngis excluded by!**/*.pngpublic/blog/coderabbit/cr-merged-pr.pngis excluded by!**/*.pngpublic/blog/coderabbit/cr-pr.pngis excluded by!**/*.pngpublic/blog/coderabbit/cr-rates.pngis excluded by!**/*.pngpublic/blog/coderabbit/cr-repos.pngis excluded by!**/*.pngpublic/blog/coderabbit/cr-request-changes-comment.pngis excluded by!**/*.pngpublic/blog/coderabbit/pr-cross-user.pngis excluded by!**/*.pngpublic/blog/coderabbit/pr-faulty-logic.pngis excluded by!**/*.pngpublic/blog/coderabbit/pr-idor.pngis excluded by!**/*.pngpublic/blog/coderabbit/pr-spoofing.pngis excluded by!**/*.pngpublic/blog/coderabbit/pr-zip-slip.pngis excluded by!**/*.pngpublic/blog/rabbit-lychee.pngis excluded by!**/*.png
📒 Files selected for processing (2)
src/content/post/2025-09-13-Code-Rabbit.mdx(1 hunks)src/navigation.js(1 hunks)
🔇 Additional comments (1)
src/content/post/2025-09-13-Code-Rabbit.mdx (1)
1-12: Assets verified — no action required All images referenced in src/content/post/2025-09-13-Code-Rabbit.mdx are present under public/blog/: public/blog/rabbit-lychee.png and public/blog/coderabbit/{analysis.png, cr-login.png, cr-repos.png, cr-loading.png, cr-pr.png, cr-request-changes-comment.png, cr-rates.png, pr-cross-user.png, pr-zip-slip.png, pr-faulty-logic.png, pr-idor.png, pr-spoofing.png}.
Summary by CodeRabbit
New Features
Documentation