rigsmith-toolslisted

Use the rigsmith CLI family — rig (convention-first dev launcher: build/test/run/ format/lint/typecheck/coverage/kill/worktree across .NET, Node, Go, Rust), changerig (changesets), shiprig (releases/publish), and clauderig (sync Claude Code config across machines + worktree/PR guard). Invoke whenever the work involves building/testing/running/formatting a project, managing changesets or changelogs, cutting or publishing a release, creating worktrees/branches, syncing Claude Code setup, finding or reopening a past Claude Code session, or working across several forked repos fused into one history (`rig stack`) — even if the user names a raw tool (go/dotnet/npm/cargo) instead of rig.
rigsmith/rigsmith · ★ 1 · Testing & QA · score 70

Install: claude install-skill rigsmith/rigsmith

# rigsmith tools A family of convention-first, zero-runtime-dependency CLIs (single static Go binaries). The same verb works in any ecosystem — each tool detects the repo and runs the right native command, sharing one project-detection engine. | Tool | Role | Reach for it when | |------|------|-------------------| | `rig` | dev launcher | building, testing, running, formatting, worktrees, branches | | `changerig` (alias `changeset`) | changesets | recording a user-facing change, bumping versions, writing CHANGELOG | | `shiprig` | releases | publishing to registries, tagging, the release pipeline | | `clauderig` | Claude Code config sync + guard | syncing `~/.claude` across machines, worktree/PR discipline | **First, confirm they're installed:** `command -v rig`. If missing, install from a rigsmith checkout with `rig source-install` (stable binaries) or `rig dev-install` (recompile-on-run `*-dev` launchers), or `curl -fsSL https://rigsmith.sh | sh`. If a stable binary is absent but a `*-dev` one exists, use that (`rig-dev`, etc.). ## Why these over running the native tool by hand Reaching for `rig build` instead of `go build ./...` / `dotnet build` / `npm run build` is not just a shortcut: - **One verb, every repo.** No remembering which ecosystem you're in or its flags. The same `rig test` / `rig coverage --min 80` works in .NET, Node, Go, and Rust. - **Shared, correct detection.** Root anchoring (`.rig.json` > solution/workspace manifest > git root), `exclude` glob