rust-setuplisted

Scaffold a new Rust repo by copying shipped template files — CI (fmt, clippy -D warnings, locked tests), pre-commit + Conventional Commits, Dependabot, git-cliff auto-release on merge to main with static binaries, crates.io Trusted Publishing (never long-lived tokens), and a tested hello-world mock (CLI bin+lib or pure library). Use only when explicitly asked to scaffold, bootstrap, or set up a new Rust repo, crate, or CLI project — invoke deliberately, e.g. "/rust-setup" or "set up a new rust repo". Not for working in existing Rust projects, and not a trigger for casual Rust questions.
bcmyguest/personal-skills · ★ 0 · AI & Automation · score 58

Install: claude install-skill bcmyguest/personal-skills

# Scaffolding a Rust repo Everything ships as **real files under [`templates/`](templates/)** — copy them verbatim, run one substitution pass, make the few marked edits. Do **not** retype configs from memory or improvise structure: the templates are the source of truth (lifted from a working repo, [powerline-claude](https://github.com/bcmyguest/powerline-claude)), and the decisions below only change *which* files get copied. What the result looks like: logic in `src/lib.rs` (testable, hello-world mock with unit + integration tests), CI failing on any warning, hygiene + Conventional Commits enforced at commit time, Dependabot keeping deps and actions current, and — if chosen — every merge to `main` auto-releasing via git-cliff (conventional commits → semver → tag → GitHub release → crates.io). ## 0. Ask the decisions | Decision | Options | Default | | ------------------- | ---------------------------------------------- | -------------------- | | Crate name | kebab-case; must be free on crates.io if publishing | ask | | GitHub repo slug | `owner/repo` | ask | | One-line description| — | ask | | Crate type | CLI (bin + lib) · library | **CLI** | | License | `MIT OR Apache-2.0` · `AGPL-3.0-only` · other | **MIT OR Apache-2.0