rigsmith

Set up a fresh macOS or Linux machine from a curated library of 220+ developer tools and the config that makes them work (shell, CLI, git, Python, Go, Rust, Java, JS, containers, Kubernetes, cloud, IaC, data, ML, VS Code), then see what's installed and undo it cleanly.

Use it if you want a good terminal and toolchain on a new machine in minutes, picked from presets instead of copied from old dotfiles, and removable without leftovers.

Look elsewhere if you need per-project package isolation or fully declarative machines (that's Nix), or a shell other than zsh (zsh only, for now).

Install

curl -fsSL https://raw.githubusercontent.com/slimfrkha/rigsmith/main/install.sh | sh -s -- install

The script installs uv if it's missing, then runs rigsmith. If you already have uv: uvx rigsmith install.

Supported: macOS 14+ (Apple Silicon and Intel), Ubuntu 22.04 / 24.04, Debian 12 (amd64, arm64). Homebrew is the package manager on both, with apt for the few things that need it.

Quickstart

1. Pick a preset for your kind of work:

   rigsmith use platform
   

   ✓ now using your config (~/.config/rigsmith/config.yaml, from platform): 97 artifacts
   

2. See what would change, without changing anything:

   rigsmith install --dry-run
   

   config: your config (~/.config/rigsmith/config.yaml, from platform)
   Answers: profile=standard, icons=yes, aliases=yes, tui=yes, theme=catppuccin, container-runtime=colima
   
   Already in place (29): git, eza, ripgrep, fd, bat, jq, gh, vscode, kubectx, k9s, terraform, …
   
   To install (55):
     + zsh — snippet 10-zsh, snippet 40-zsh
     + zinit — install git:https://github.com/zdharma-continuum/zinit.git, snippet 20-zinit
     + starship — snippet 90-starship
     …
   

   What's "already in place" depends on your machine: those are left alone.

3. Install: rigsmith install. A short questionnaire and a picker let you change anything before a final confirmation, then tools install one after the other. Open a new terminal when it's done.

Commands

install, scan and uninstall filter with -c CONFIG, -p PROFILE, -s SECTION[/SUB] and artifact ids. Every flag is in the reference.

Presets

The developer presets share a base (zsh, starship, fzf, ripgrep, eza, zoxide, git, lazygit, VS Code); server keeps only the shell and CLI part. Every preset pins its answers, so -y gives the same result every time. reference has every tool; example is the author's own setup. The first rigsmith install asks which to start from:

How it works

• Artifact: one installable unit: a package plus the config the tool needs to work (a zsh snippet, a few settings). Optional taste, like aliases or a theme, is a separate artifact you can leave out.
• Section: what a tool is (cli/search, kubernetes/logs). Profile: how much you want (minimal ⊂ standard ⊂ comprehensive).
• Role: tools that can't coexist, such as two prompts. You get one, and a tool you already have is kept.
• Questions are built from what's in scope: icons, aliases, full-screen apps, theme, your work folder and email.

Safe by design

• Your ~/.zshrc is never overwritten. rigsmith adds one marked block at the top; your own lines stay below and win.
• Every change gets a receipt, recording the value before and the value rigsmith left. uninstall undoes only what rigsmith did, and keeps anything you changed since.
• Steps that can't be undone are listed before you confirm, such as installing Homebrew.
• Nothing is a black box. --script prints every command an install or uninstall would run, for reading (why you shouldn't run it yourself).
• Running it again changes nothing. CI installs, reinstalls (expecting 0 changes) and uninstalls on real macOS and Ubuntu machines, and checks ~/.zshrc comes back byte for byte.

Where next

License

MIT