Repository navigation
docs: record the latest listings and submissions - #931
Conversation
- pegaltier/awesome-utils-dev merged, so it moves to Listed. - The Gemini CLI gallery lists the plugin now. - New submissions: the mcpm.sh registry and the Kilo marketplace join the directories, and mcpHQ/awesome-mcp-servers joins the lists in review. - cursor.directory holds a pasted copy of each skill's text, so its row and a new "Editing a skill" bullet say the copies need refreshing when a skill changes. The bestax-mcp bullets name the new entries that give the npx command or list the tools. - The naming note adds that every description says early on that Bestax is for building with Bulma v1.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 13 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (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 |
Preview DeploymentPreview URL: https://d9ef8f79.bestax.pages.dev |
There was a problem hiding this comment.
Deep review — 0 blocking · 2 advisory
| # | Severity | Area | Finding | Location |
|---|---|---|---|---|
| 1 | 🔵 Advisory | Correctness | The new "every description says early on … Bulma v1" claim is contradicted by bestax-mcp/server.json and create-bestax's own descriptions, and by the hedged form three lines above it |
docs/docs/guides/distribution.md:176 |
| 2 | 🔵 Advisory | Robustness | Both new entries restate engines.node: ">=22", and no What goes stale bullet tracks the Node floor |
docs/docs/guides/distribution.md:51 |
Overall: Docs-only, and every externally checkable claim it makes holds up — I pulled all four referenced pull requests through the API and the status this page gives each of them is right. The riskiest part is not the diff but the thing the page exists to prevent: it adds two listings whose submitted text restates repo facts, and only some of those facts have a What goes stale bullet behind them. Look at finding 1 first — it is the one sentence here that an auditor would act on and find false.
Evidence checked
| Claim in the diff | Checked against | Result |
|---|---|---|
| pegaltier/awesome-utils-dev merged, so it moves to Listed | GET /repos/pegaltier/awesome-utils-dev/pulls/81 |
merged: true, 2026-10-06 ✓ |
| mcpm.sh #427 in review | GET /repos/pathintegral-institute/mcpm.sh/pulls/427 |
state: open ✓ |
| Kilo #339 in review | GET /repos/Kilo-Org/kilo-marketplace/pulls/339 |
state: open ✓ |
| mcpHQ #135 in review | GET /repos/mcpHQ/awesome-mcp-servers/pulls/135 |
state: open ✓ |
mcpm.sh entry gives npx -y bestax-mcp@1 and lists each tool by name |
PR files: mcp-registry/servers/bestax-mcp.json |
args: ["-y", "bestax-mcp@1"], plus a tools array naming each one ✓ |
Kilo entry gives npx -y bestax-mcp@1 |
PR files: mcps/bestax-mcp/MCP.yaml |
args: ["-y", "bestax-mcp@1"] ✓ |
| mcpHQ belongs under Awesome lists, Entry = Bestax | PR files: README.md, data/servers.json |
a README list entry linking tree/main/bestax-mcp ✓ |
| Gemini row: bestax-skills has both the file and the topic | GET /repos/allxsmith/bestax-skills plus gemini-extension.json |
topics: ["gemini-cli-extension"], file present ✓ |
Residual risk:
- A bestax.io page move still breaks a deep link no bullet names. mcpm.sh #427 sets its
homepagetohttps://bestax.io/docs/guides/llms#mcp-server, andbestax-mcp/server.jsonalready carries the same URL aswebsiteUrlfor the Official MCP Registry row — but the "Renaming a package or moving a page on bestax.io" bullet enumerates onlyhttps://bestax.io,/llms.txtand/llms-full.txt. Open, but not introduced here: theserver.jsoncase predates this PR, so it is a standing gap in the page rather than a defect in the diff. - The mcpHQ entry's restated facts are already covered. Its description (props, examples, CSS variables and Agent Skills) falls under the "Changing what
bestax-mcpoffers" bullet, and itstree/main/bestax-mcpURL under "Moving or renaming a package folder". Refuted by reading the submittedREADME.mdanddata/servers.jsondiff against both bullets. - The new prose does not trip
fragile-prose. Readscripts/lib/fragile-prose.mjsdirectly:#427,#339and#135are blanked by the issue-reference mask,npx -y bestax-mcp@1sits in inline code whichstripSpansblanks, and "tool" is not inCOUNTED_NOUNS. A static read, not a run — see the gates note below. - Not verified, and not verifiable from here: the Gemini CLI gallery actually showing the plugin, and cursor.directory holding a pasted copy of each skill. Both are maintainer observations of third-party sites, and this session had no network egress — WebFetch and WebSearch were both denied. The repo-side mechanism the Gemini row cites does check out.
- Gates not run.
npx prettier --check docs/docs/guides/distribution.mdandnode scripts/check-conformance.mjs --only=fragile-prosewere both refused by this sandbox's permission layer, confirmed twice including from a subagent, soformat:checkand conformance are unverified by me. The diff re-pads both reworked tables wholesale, which is what prettier does when a wider row lands, but CI is the authority — do not read this review as a green format check.
🏄 Pure paperwork swell, dude — four pull requests checked, four come back legit, nothing in the lineup that is gonna wipe you out. Trim that one "every" before it eats you and this one is good to paddle out on.
The naming note said every description already leads with Bulma v1, but older ones, like the one in bestax-mcp/server.json, put it last. It now asks new and refreshed descriptions to lead with it. The mcpm.sh and Kilo entries repeat bestax-mcp's Node engines floor, so a new "What goes stale" bullet names them for when that floor rises.
Preview DeploymentPreview URL: https://aabac946.bestax.pages.dev |
There was a problem hiding this comment.
Deep review (verify) — 2 resolved · 0 open
| # | Severity | Area | Thread | Outcome |
|---|---|---|---|---|
| 1 | 🔵 Advisory | Correctness | The naming note claimed every description leads with Bulma v1 | ✅ Verified fixed · resolved |
| 2 | 🔵 Advisory | Robustness | Node floor restated by two entries, untracked in What goes stale | ✅ Verified fixed · resolved |
Overall: This pass settled threads and reviewed no commits. Both advisories the prior review left open are addressed by ce09f96: the naming note at docs/docs/guides/distribution.md:178-180 now asks that a new or refreshed description lead with Bulma v1 and says outright that older entries such as bestax-mcp/server.json still put it last, which matches that file, and distribution.md:161-162 adds a What goes stale bullet naming the mcpm.sh registry and the Kilo marketplace as repeating the engines floor from bestax-mcp/package.json, which is node: ">=22" there. Nothing of mine is left open, so a maintainer wanting the current text reviewed afresh should steer with deep-review: fresh.
Residual risk: Not assessed — a verify pass settles the prior review threads and raises nothing new. For the record, pnpm run check:conformance is green across all 23 checks, fragile-prose and listings-sync included, and prettier reports the page formatted.
🏄 Couple of mellow advisories rolled in on the last set, and the author paddled straight back out and cleaned both up — note softened, Node floor added to the stale list. Glassy conditions, nothing left in the lineup. Good to go.
|
🎉 This PR is included in version 5.26.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 4.2.13 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.25.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.14.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Brings the distribution page up to date.