CLI Reference

Wick ships two kinds of commands:

• Built-in commands are hardcoded in the wick binary (init, run, skill, upgrade, version). They work the same across every project and the behavior is fixed by the installed wick version.
• Task shortcuts (dev, setup, build, test, tidy, generate) are thin wrappers that execute the matching task in your project's wick.yml. You can edit or extend those tasks per project; wick run <task> runs any arbitrary task defined there.

Run wick --help to print the current list.

---

Built-in commands

wick init [name]

Scaffold a new wick project in ./<name> (default: myapp).

wick init my-app
wick init my-app --skip-setup   # skip "go mod tidy" and "wick setup"

Copies the bundled template (tools, jobs, tags, wick.yml, AGENTS.md, example tool and job) and the shared design-system skill into ./.claude/skills/design-system/.

---

wick run <task>

Execute an arbitrary task from wick.yml. Useful for tasks that don't have a dedicated shortcut.

wick run css        # runs the "css" task from wick.yml
wick run clean

Shortcuts below (dev, setup, etc.) are equivalent to wick run <name>.

---

wick skill list

List the AI agent skills bundled with the installed wick binary.

$ wick skill list
tool-module
design-system

---

wick skill sync [name...]

Replace ./.claude/skills/<name>/ with the bundled version. Use this after upgrading wick to pull in updated skill content.

wick skill sync                       # sync all bundled skills
wick skill sync design-system         # sync one
wick skill sync tool-module design-system

Side effects on ./AGENTS.md:

• Missing — a fresh AGENTS.md is written from the bundled template (same file shipped by wick init).
• Present, skill table matches the default shape — the body of the | Task | Skill | table is regenerated from the bundled skill list. Labels for known skills come from wick's internal map; unknown skills fall back to the skill name.
• Present, skill table is customized (rows don't link to ./.claude/skills/<name>/SKILL.md) — left untouched. Edit by hand if you want the new skills listed.

The skill folder contents are always replaced — local edits inside ./.claude/skills/<name>/ will be overwritten. Commit anything you want to keep.

---

wick upgrade

Bump the github.com/yogasw/wick dependency in the current project's go.mod to the latest released version, then tidy and run dev.

$ wick upgrade
current: v0.1.13
latest:  v0.2.0
upgrade v0.1.13 -> v0.2.0? [y/N]: y
> go get github.com/yogasw/wick@v0.3.0
> go mod tidy
> <dev task from wick.yml>

Steps:

1. Read the pinned version from the require block in ./go.mod.
2. Fetch the latest version from https://proxy.golang.org/github.com/yogasw/wick/@latest.
3. If already on latest, exit without prompting.
4. Otherwise prompt [y/N]; only y/yes proceeds.
5. Run go get github.com/yogasw/wick@v0.3.0, then go mod tidy, then the dev task from wick.yml.

Run from a project directory (one that has a go.mod requiring github.com/yogasw/wick).

---

wick version

Print the installed wick version.

$ wick version
v0.1.12

---

Task shortcuts (from wick.yml)

Each of these runs the matching task in wick.yml. The commands shown in the "Default behavior" column are what the template ships — edit wick.yml to change them.

Command	Default behavior
wick setup	Download Tailwind + templ into ./bin/, run go mod tidy
wick dev	Generate templ + CSS, start go run . server
wick build	Generate + minify CSS, compile binary to bin/app
wick generate	Regenerate templ, run go generate ./..., rebuild CSS
wick test	go test ./... -coverprofile=./coverage.out
wick tidy	go fmt ./... + go mod tidy -v

See wick.yml reference for the full task syntax (if_missing, download, bg, variable interpolation, etc.).