Update flashinfer-bench doc link

[xslingcn]

Summary by CodeRabbit

• Documentation
  • Updated the FlashInfer-Bench leaderboard link to the correct URL.
  • Fixed markdown quote/formatting in the blog post for clearer reading.
  • Added and repositioned leaderboard screenshots to improve visual clarity of the leaderboard section.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (2)

• assets/imgs/flashinfer-bench/image14.png is excluded by !**/*.png
• assets/imgs/flashinfer-bench/image15.png is excluded by !**/*.png

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

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

Updated a blog post: corrected a Leaderboard hyperlink from flashinfer_trace to flashinfer-trace, fixed a blockquote formatting, and inserted two figure blocks referencing image16.png in the Leaderboard section (one after the heading, one before the existing image15.png figure).

Changes

Cohort / File(s)	Summary
Blog Post Update \_posts/2025-10-21-flashinfer-bench.md	Fixed hyperlink (flashinfer_trace → flashinfer-trace), corrected markdown/quote formatting, added two figure blocks with image16.png (one after the "FlashInfer-Bench Leaderboard" heading, one before the existing image15.png figure).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• PR Add FlashInfer-Bench blog post #5: Introduced the _posts/2025-10-21-flashinfer-bench.md blog post being edited here (same file; related formatting/link/image changes).

Suggested reviewers

• Ubospica
• yzh119

Poem

🐰 A dash became a kebab, tidy and neat,
Screenshots multiplied for a leaderboard treat.
I hopped through the markdown, fixed quotes with delight,
Now images and links all sit just right. 🥕✨

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 PR title "Update flashinfer-bench doc link" directly corresponds to the primary change documented in the summary: updating the Leaderboard link from "flashinfer_trace" to "flashinfer-trace." The title is concise, specific, and clearly communicates the main objective of this changeset. While the summary mentions additional modifications such as markdown formatting corrections and screenshot insertions, the link update appears to be the central intent, as reflected in the author's choice of title. The title successfully summarizes the key change without unnecessary verbosity or vague terminology.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

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

[gemini-code-assist]

Summary of Changes

Hello @xslingcn, 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 focuses on refining the flashinfer-bench documentation by addressing two key areas: correcting an outdated link and enriching the visual content. The primary goal is to ensure that readers have access to accurate information and a more comprehensive visual experience within the post.

Highlights

• Documentation Link Correction: The URL for the 'FlashInfer Trace' documentation has been updated to reflect the correct path, changing flashinfer_trace/flashinfer_trace to flashinfer-trace.
• New Image Addition: A new image (image16.png) has been added to the 'FlashInfer-Bench Leaderboard' section, enhancing the visual content of the post.

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 updates a documentation link and adds an image to the flashinfer-bench.md blog post. The link update is correct, but I've pointed out another instance of the same link in the file that was missed. I've also suggested improving the accessibility of the newly added image by providing more descriptive alt text. Overall, these are minor changes to improve the post's correctness and accessibility.

[gemini-code-assist]

Thanks for updating this link. However, it seems another instance of this link on line 101 was missed. Please update it as well to maintain consistency throughout the document.

The line in question is:

101: We provide standardized and clear documents for [FlashInfer Trace](https://bench.flashinfer.ai/docs/flashinfer_trace/flashinfer_trace) and [Op Types](https://bench.flashinfer.ai/docs/op_type_schema/gemm).

[gemini-code-assist]

The alt text for this image is identical to the one for the image on line 152. To improve accessibility for users with screen readers, it's best practice to provide unique and descriptive alt text for each image that conveys its specific content. Please consider updating the alt text to describe what this particular image shows.