cw init

Bootstrap Commit Wizard config assets for a project, user, or registry. When run with no subcommand it initialises a hidden project config (.cwizard.toml) using the standard profile.

Usage

cw init [OPTIONS] [SUBCOMMAND]

Subcommands

Subcommand Description
project Create a project config (.cwizard.toml) in the current directory
config Create a config file (project or global)
rules Create a rules file (project or global)
registry <PATH> Scaffold a new registry at the given path

Examples

Quickstart — create .cwizard.toml with the standard profile:

cw init

Minimal config (fewest required fields):

cw init --minimal

Full config (every available field with defaults):

cw init --full

Use a named profile:

cw init --profile standard

Set values inline during init:

cw init --set commit.scopes.mode=required --set versioning.tag_prefix=v

Init a global config:

cw init config --global

Init a global rules file:

cw init rules --global

Scaffold a registry with rules support and two sections:

cw init registry ./path/to/registry --rules --section frontend --section backend

Init a visible project config (cwizard.toml instead of .cwizard.toml):

cw init project

Options

Flag Conflicts with Description
--minimal --full, --profile Generate a minimal config with only required fields
--full --minimal, --profile Generate a full config with all fields
--profile <PROFILE> --minimal, --full Profile: minimal, standard (default), full
--set <KEY=VALUE> Inline key-value overrides; may be repeated

Subcommand-specific flags

project:

Flag Description
--hidden Write to .cwizard.toml (default for cw init with no subcommand)

config, rules:

Flag Short Description
--global -g Write to the global config/rules location

registry <PATH>:

Flag Description
--rules Include a rules.toml file in the registry
--section <NAME> Create a named subdirectory section; may be repeated

Profiles

Profile Description
minimal Only the fields you're most likely to customise
standard Sensible defaults for most teams (default)
full Every supported field, useful as a reference

Global flags

All global flags are supported. Use --dry-run to preview what would be written without creating any files.