One command to scaffold a devrig workspace — no cloning, no separate setup step.

English · 简体中文 · Español · हिन्दी · Português · 日本語 · Français · 한국어 · සිංහල

npx create-devrig my-project

That's it. This one command:

1. Fetches the devrig template into my-project/ — no git history, just the files.
2. Strips devrig's own repo furniture (branding assets, translated docs, CITATION.cff, CONTRIBUTING.md, LICENSE) so the workspace starts clean — it's your project, not devrig's.
3. Initializes a fresh git repository there.
4. Launches devrig's interactive setup wizard immediately, so you configure your project name, description, GitHub org, repos, issue tracker, and feature toggles in the same command — the wizard also generates a README.md for your project in place of devrig's.

Omit the directory and you'll be prompted for one:

npx create-devrig

Requirements

| | | |---|---| | Node.js | 18+ | | git | required — used to fetch the template and initialize your new repo | | bash | native on macOS/Linux. On Windows, run this inside WSL or Git Bash — devrig's setup.sh is a bash script |

What this package does not do

It doesn't reimplement any of devrig's setup logic — it only fetches the template, trims the template-only files, and hands off to its own setup.sh (which trims them too, so the GitHub "Use this template" path ends up identical). Updates to devrig's setup flow, skills, or config schema take effect automatically the next time someone runs npx create-devrig; this package itself rarely needs to change.

Prefer not to use npx?

GitHub's UI works just as well:

1. Click Use this template on the devrig repo.
2. Clone it and run ./setup.sh yourself.

Both paths land you in the exact same interactive wizard.

Contributing

This package is intentionally tiny — one file, one dependency (degit). Bug reports and small fixes are welcome via issues or a PR. If what you actually want to change is the setup flow, skills, or config schema, that lives in devrig itself, not here.

License

MIT — see LICENSE.