react-doctor
Skill4 starsChanged 55 days agoLicence not identifiedView on GitHub
Diagnostic React/Next post-vibecoding : pose l'outillage déterministe (lint hooks) au lieu de le paraphraser, audite les pathologies que le lint ne voit pas (useEffect pour état dérivé, frontière server/client, secrets dans le bundle client, instanciation module-level), et prouve les findings perf par mesure de re-renders dans la vraie app. Use when: « diagnostique ce repo React », « pourquoi ça re-render », « passe react-doctor », ou /react-doctor sur un repo React/Next. Uniquement sur demande explicite.
52 other projects use a version of this.
Adopted by
Most recently taken up by
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- uptimekit/uptimekittheir own version, first seen Nov 8, 2026
- PunGrumpy/docker-doctortheir own version, first seen Nov 8, 2026
- compozy/compozytheir own version, first seen Nov 7, 2026
- PostHog/posthog-fosstheir own version, first seen Nov 6, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 3, 2026
Used with
Projects with it also use turborepo, make-interfaces-feel-better and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkillturborepo
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries.
Also in 5 projects that use this
studio-lgtmSkillmake-interfaces-feel-better
Apply design engineering best practices to polish UI components - use when reviewing or improving interfaces, animations, typography, or interaction details.
Also in 4 projects that use this
AnasX7Skillbetter-accessibility
Helps your project comply with accessibility standards and best practices.
Also in 3 projects that use this
- AnasX7Skill
better-layout
Helps with grouping, alignment, reading order, progressive disclosure and other details that make a good layout.
Also in 3 projects that use this
SentrySkillvercel-composition-patterns
Also in 6 projects that use this
VercelSkillgh-stack
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.
Also in 3 projects that use this
- +2 more from AnasX7
Other versions52 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 52
- makeplane/plane★ 62ksame name
- gogs/gogs★ 48ksame name
- PostHog/posthog★ 40ksame name
- millionco/react-doctor★ 15ksame name
- humanlayer/humanlayer★ 13ksame name
- ArcReel/ArcReel★ 6.3ksame name
- transformerlab/transformerlab-app★ 5.2ksame name
- pgrok/pgrok★ 3.6ksame name
- Shelf-nu/shelf.nu★ 3.1ksame name
- compozy/compozy★ 2.9ksame name
42 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 repository10 other files it gives its agents.
- cleanup-passSkill
- doc-ingestSkill
- docs-passSkill
- excalidraw-slidesSkill
- fluid-passSkill
- llm-handoverSkill
- proof-runSkill
- safety-netSkill
- ship-checkSkill
- spec-liteSkill
The file
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 51 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.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 51 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.
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.