Uninstall
Portable dev practices, packaged as skills - that run inside the coding agent you already use (Claude Code, Codex, pi, hermes). Not an agent, framework, or provider layer.
npx -y skills add yoelgal/better-dev --skill uninstallAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a person wants to remove better-dev - unwire a repo (drop the .better-dev/bin bridge and optionally the CLAUDE.md/AGENTS.md block) or remove the global per-host install. Never deletes your rules, overrides, or learnings unless you ask.
SKILL.md
2.0 KB, 413 tokens by cl100k_base, as published. Nobody here has run it
Uninstall better-dev
Removing better-dev is deliberate, so this skill is user-invoked. The work is one script,
.better-dev/bin/bd-uninstall (in the clone, scripts/bd-uninstall); it removes only what better-dev
installed and leaves everything else in place.
The safety default is dry-run: every command below first prints exactly what it would remove and changes
nothing. Read that plan, then re-run with --yes to act.
Two things to remove
-
This repo's wiring - the per-machine
.better-dev/binbridge, and (on request) the managed discovery block inCLAUDE.md/AGENTS.md:.better-dev/bin/bd-uninstall repo # dry-run: show what would go .better-dev/bin/bd-uninstall repo --unblock --yes # drop the bridge and the managed block -
The global per-host install - the per-skill links in each host's skills dir and the install marker:
.better-dev/bin/bd-uninstall global # dry-run across detected hosts .better-dev/bin/bd-uninstall global --yes # remove better-dev's links; leave foreign skillsA same-named skill that isn't better-dev's is never touched; the report names what it left and why.
Your data survives
bd-uninstall repo leaves .better-dev/rules.md, overrides.md, learnings.jsonl, and the loop
ledger/ in place. They are only removed when you add --purge-data, and the dry-run shows them before
anything is deleted. If you want a clean unwire but want to keep your project's learnings, that is the
default - just omit the flag.
The removal is script-driven; when in doubt, run the dry-run and read its report before adding --yes.