millionco/react-doctor

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 babysit until mergeable.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/millionco/react-doctor --skill ship

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Ship

Sequential release pipeline for the current branch. Run only when explicitly invoked — it commits, pushes, and opens a PR.

Each stage delegates to an existing skill. Run them in order and do not advance while a stage still has unresolved findings.

Copy this checklist and track progress:

Ship progress:
- [ ] 1. Review the diff against AGENTS.md
- [ ] 2. Deslop the touched code
- [ ] 3. Commit and push
- [ ] 4. Open the PR
- [ ] 5. Babysit to merge-ready

1. Review against AGENTS.md

Read AGENTS.md first (its rules change), then run /review on this branch's diff, judging it against those rules. Fix real violations before continuing. Pause for the user only if a fix would change behavior or broaden scope.

2. Deslop

Run /deslop (`../deslop/SKILL.md`) to simplify the recently modified code while preserving functionality, including its truffler duplicate-consolidation pass. Apply the refinements before committing.

3. Commit and push

  • Stage only the intended changes; never commit secrets.
  • Add a changeset first when a published package's behavior changed (follow the Changeset section of /rule-validate); skip only for private/docs/test/tooling-only changes and note why.
  • Run the repo checks that fit the change before committing: nr test, nr lint, nr typecheck, nr format:check.
  • Write a concise commit message in the repo's style, focused on the why.
  • Push the branch, setting upstream with -u on the first push.
  • Git safety: no force-push to main, no skipped hooks, no git config changes.

4. Open the PR

Create the PR with gh pr create, writing the body with the PR Description structure from /rule-validate (`../rule-validate/SKILL.md`): Why (with before/after), What changed, Eval results (omit the table if RDE was not run), Test plan. Pass the body via a heredoc. Return the PR URL.

5. Babysit

Run /babysit to drive the PR to merge-ready: resolve merge conflicts preserving intent, triage unresolved comments (including Bugbot), and fix in-scope CI in a loop until the PR is mergeable, green, and its comments are triaged. Report back instead of merging.

Stop conditions

Pause and ask the user when:

  • Review or babysit surfaces a change that would broaden scope or alter intended behavior.
  • A merge conflict has genuinely conflicting intent on the two branches.
  • CI fails for reasons outside this branch's scope even after merging the latest base.

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
millionco
Communauté

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 canonical playbook.

Installations / 1h
2
GitHub Stars
15,2 k
Mis à jour
20 nov.
millionco
Communauté

improve-threejs

Audit and fix Three.js and React Three Fiber apps for frame-loop performance, GPU memory leaks, scene-graph correctness, and visual defects like z-fighting, shadow acne, wrong color space, and broken resize handling. Uses React Doctor as the scanning engine plus a visual rubric checked against rendered output. Use when the user asks to improve, audit, scan, or clean up a Three.js, R3F, react-three-fiber, drei, or WebGL app, or types /improve-threejs.

Installations / 1h
2
GitHub Stars
15,2 k
Mis à jour
19 nov.
millionco
Communauté

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.

Installations / 1h
1
GitHub Stars
15,1 k
Mis à jour
7 nov.
millionco
Communauté

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.

Installations / 1h
1
GitHub Stars
15,1 k
Mis à jour
7 nov.