review-docs
Skill1.2k starsChanged 21 days agoApache-2.0View on GitHub
Review and fix ChatJS Blume documentation and MDX files. Use when checking docs for correctness, broken links, stale examples, unclear prose, or consistency with the implementation.
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read each target file completely and verify code examples, paths, terminology, and behavior against the repository.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review ChatJS documentation
Read each target file completely and verify code examples, paths, terminology, and behavior against the repository.
Fix directly when the correct change is clear:
- Typos, grammar, formatting, and unclear phrasing
- Broken links and incorrect paths
- Stale examples with an evident replacement in the codebase
- Missing imports and inconsistent terminology
- Dead external links
Report only issues that require a product, architecture, or domain decision. Summarize edited files and list any remaining decisions with context and concrete options.
Trending
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Other versions22 projects use a version of this.
Word for word · 2
- FranciscoMoretti/chat-js★ 1.2k100% same
- FranciscoMoretti/sparka★ 1.2k100% same
Edited · 0
None found.
Wrote their own version · 20
- tldraw/tldraw★ 51ksame name
- videojs/video.js★ 40ksame name
- reactjs/react.dev★ 12ksame name
- hashicorp/terraform-provider-aws★ 11ksame name
- JamieMason/syncpack★ 2.1ksame name
- OpenAEV-Platform/openaev★ 1.8ksame name
- Kaggle/kaggle-environments★ 456same name
- JetBrains/youtrackdb★ 442same name
- thoughtfulllc/gridland★ 363same name
- heypinchy/pinchy★ 184same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- check-visual-changesSkill
- create-vercel-ai-issueSkill
- dev-auth-bypassSkill
- economical-visual-testsSkill
- generate-code-snippetSkill
- lazy-prefetch-patternSkill
- making-ui-changesSkill
- next-cache-components-adoptionSkill
- next-dev-loopSkill
- next-partial-prefetching-adoptionSkill
- strategic-testingSkill
- triage-visual-changesSkill
- trpc-patternsSkill
- vitest-visual-testingSkill
- worktree-portsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.