프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. Google로 로그인하면 리뷰를 쓸 수 있어요.프로토타입 · 30분마다 업데이트
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

react-doctor Skill

제작자: millionco★ 15,139 (whole repo)skill 14개

★ Stars are for the whole repo, not each skill

Pick the skill to install

What it does

This repo is a collection of 14 skills

  • Connects Instruction files the AI reads; connects to nothing
  • Account or key No key needed
  • Category 코딩
Maker’s original description
Your agent writes bad React. This catches it
제작자용: README에 배지 달기

제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/millionco-react-doctor.svg)](https://mcp.popnx.com/en/skills/millionco-react-doctor)

함께 쓰기

같은 작업에서 AI를 서비스에 연결하는 MCP

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

제작자: morluto널리 사용됨↓ 38.9만/주★ 46.2만4일 전 업데이트

MCP · 서비스 연결내 컴퓨터에서 실행

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

제작자: fallow-rs널리 사용됨↓ 244.1만/주★ 5.4천어제 업데이트

MCP · 서비스 연결내 컴퓨터에서 실행

Desktop Commander

MCP server for terminal commands, file operations, and process management

제작자: wonderwhy-er널리 사용됨↓ 74만/주★ 1만4일 전 업데이트

MCP · 서비스 연결내 컴퓨터에서 실행

비슷한 Skill

같은 종류의 작업, Skill 목록과 같은 순서

비슷한 항목과 비교
이 항목
react-doctor
reagraphifyarchifysecurity-audit-skill
제작자millioncomorlutoGraphify-Labstt-a1icloudflare
Skill 수141111
GitHub 별15,139461,751148,35296,75773,156
마지막 코드 변경2026년 11월 14일2026년 11월 16일2026년 11월 16일2026년 11월 15일2026년 9월 15일
라이선스–MITApache-2.0Apache-2.0MIT

millionco의 Skill(지시 묶음) 14개, AI가 읽고 그대로 일해요 · MCP server가 아니에요

Pick the skill to install

Install only the ones you use. Open a skill to see how to install it

Install the whole set (14)

If you want every one, let the AI install them in one go. Know 2 things first

  • Every installed skill’s description is loaded into every chat. The more you install, the easier it is for the AI to pick the wrong one
  • Some skills duplicate tools the AI already has built in. Installing only the ones you use works better
Where to install
Please install all 14 skills from https://github.com/millionco/react-doctor: benchmark-fp-fn-audit, deslop, find-similar-functions, fuzz, improve-react, product-thinking, rde-eval, react-doctor, rule-research, rule-validate, rule-writing, run-parity, ship, writing-guidelines, for all my projects, putting each at ~/.claude/skills/<skill name> (in Codex use ~/.agents/skills/<skill name>, in Cursor ~/.cursor/skills/<skill name>). Folders in the repo: benchmark-fp-fn-audit = .agents/skills/benchmark-fp-fn-audit · deslop = .agents/skills/deslop · find-similar-functions = .agents/skills/find-similar-functions · fuzz = .agents/skills/fuzz · improve-react = skills/improve-react · product-thinking = .agents/skills/product-thinking · rde-eval = .agents/skills/rde-eval · react-doctor = skills/react-doctor · rule-research = .agents/skills/rule-research · rule-validate = .agents/skills/rule-validate · rule-writing = .agents/skills/rule-writing · run-parity = .agents/skills/run-parity · ship = .agents/skills/ship · writing-guidelines = .agents/skills/writing-guidelines. First show me every file and tell me whether any has scripts or changes machine settings, then tell me the full path you will install each one to and wait for me to agree.
Please install all 14 skills from https://github.com/millionco/react-doctor: benchmark-fp-fn-audit, deslop, find-similar-functions, fuzz, improve-react, product-thinking, rde-eval, react-doctor, rule-research, rule-validate, rule-writing, run-parity, ship, writing-guidelines, into the project this chat is open in (at .claude/skills/<skill name>; in Codex use .agents/skills/<skill name>, in Cursor .cursor/skills/<skill name>). Folders in the repo: benchmark-fp-fn-audit = .agents/skills/benchmark-fp-fn-audit · deslop = .agents/skills/deslop · find-similar-functions = .agents/skills/find-similar-functions · fuzz = .agents/skills/fuzz · improve-react = skills/improve-react · product-thinking = .agents/skills/product-thinking · rde-eval = .agents/skills/rde-eval · react-doctor = skills/react-doctor · rule-research = .agents/skills/rule-research · rule-validate = .agents/skills/rule-validate · rule-writing = .agents/skills/rule-writing · run-parity = .agents/skills/run-parity · ship = .agents/skills/ship · writing-guidelines = .agents/skills/writing-guidelines. First show me every file and tell me whether any has scripts or changes machine settings, then tell me the project name and the full path you will install each one to and wait for me to agree.

Uploading to Claude on the web and apps: you need 14 uploads, one ZIP per skill. Open each skill in the list below to download it

Checked against official docs 2026년 11월 12일 · Source: support.claude.com, code.claude.com, learn.chatgpt.com, cursor.com

  • benchmark-fp-fn-audit

    Audit React Doctor against ReactBench or similar diagnostic benchmark corpora for confirmed false positives, false negatives, taxonomy gaps, and verifier artifacts. Use when analyzing rd.log, rd-before.json, rd-after.json, model.patch, result.json, reward/test logs, rule distributions, or when aske…

  • deslop

    Simplify and refine recently modified code while preserving functionality. Use when asked to "deslop", "clean up code", "simplify code", or after making changes that could benefit from refinement.

  • find-similar-functions

    Use truffler to find similar or pre-existing JavaScript/TypeScript symbols before implementing new code, especially helpers, utilities, parsers, formatters, scanners, fuzzy matchers, and other reusable functions. Agents should use this skill whenever they are about to add or refactor functionality…

  • fuzz

    Fuzz React Doctor rules for crashes, slowness, false positives, and mutation-sensitive diagnostics with @react-doctor/fuzz. Use after rule tests pass, when investigating a fuzz finding, or whenever an eval, review, or user report confirms a new false positive.

  • improve-react

    Survey a whole React codebase as a senior React engineer, using React Doctor's scan as evidence, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use wh…

  • product-thinking

    Think like a product manager before changing React Doctor's public surface — CLI commands/flags, the 0–100 score, config (doctor.config.*), the JSON report schema, package APIs (inspect()/diagnose()), the GitHub Action, the website, and the canonical prompts. A step-by-step runbook for a user-facin…

  • rde-eval

    Run a targeted local React Doctor Evals loop against an uncommitted rule change. Use after focused rule tests pass, while inspecting real open-source hits, or when rule-validate needs local false-positive evidence before pull request parity.

  • react-doctor

    Use when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canon…

  • rule-research

    Define a precise React Doctor rule contract before implementation. Use when validating a rule idea, collecting official or open-source evidence, identifying false-positive traps, choosing detector precision, or setting first-version boundaries.

  • rule-validate

    Validate an implemented React Doctor rule before merge. Use after focused tests pass to review detector correctness, inspect open-source hits, run pull request parity, add regression coverage, prepare a changeset, write pull request copy, or address review findings.

  • rule-writing

    Implement React Doctor rules from a validated contract. Use when writing oxlint rules, planning syntax or control-flow detection, designing adversarial tests, reusing syntax tree utilities, or updating rule registration.

  • run-parity

    Compare React Doctor diagnostics for a GitHub pull request (PR) with Vercel Sandbox. Use when asked to run parity, check a PR for diagnostic regressions, compare a PR with its base, or report added and removed diagnostics.

  • ship

    Take the current branch from done-coding to merge-ready in one pass — review the diff against AGENTS.md, deslop, commit and push, open a PR using rule-validate's PR copy, then monitor checks and reviews until mergeable. Use when the user types `/ship` or asks to ship, finalize, or land the current…

  • writing-guidelines

    Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".

Skill과 MCP의 차이

MCP = 손

AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.

Skill = 안내서

작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.

겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.

쓸 수 있는 앱

Codex

제작자 README와 repo 폴더 기준

설치

Pick a skill first

This repo has 14 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP

Let the AI install it
Upload to claude.ai

Go to the skill list ↑

토론

질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.

아직 글이 없어요. 처음으로 질문하거나 공유해 보세요.

이곳의 글은 사용자가 쓴 것으로, PopNx 팀의 글이 아니에요.

로그인하고 글쓰기

GitHub 정보

GitHub 스타
15,139
Stars are for the whole repo, not each skill
제작자
millionco
라이선스
밝히지 않음
최근 코드 수정
2026년 11월 14일
repo 안 SKILL.md(번역본과 템플릿 포함)
15
토픽
agents, code-review, doctor, react, skill