tusk-initlisted

# Tusk Init — Project Setup Wizard Interactive config wizard. Scans the codebase, suggests project-specific values, writes the final config. ## Step 1: Check for Existing Tasks ```bash tusk "SELECT COUNT(*) FROM tasks;" ``` - **Non-zero task count**: offer backup (`cp "$(tusk path)" "$(tusk path).bak"`), warn that `tusk init --force` destroys all existing tasks. Stop if user declines. - **Zero tasks**: proceed without warning. ## Step 1.5: Detect / Initialize Git Repository Tusk works best inside a git repository — branch-per-task, commit history, and hooks all assume one. `install.sh` no longer requires a git repo to run, so fresh projects may reach this skill without one. Detect: ```bash git rev-parse --show-toplevel >/dev/null 2>&1 && echo "git" || echo "no-git" ``` - **`git`** — proceed to Step 2 silently. - **`no-git`** — ask the user a single yes/no: > No git repository detected at the project root. Tusk relies on git for branch-per-task tracking, commit hashing, and hooks. Run `git init` here? > > Options: **yes** (init now) · **no** (continue without git — branch/commit/merge features will be limited) - **yes** — run `git init` and continue to Step 2. - **no** — print a one-line warning and continue to Step 2: `Skipped git init — branch/commit features will fail until a repo exists.` ## Step 2: Scan the Codebase Gather project context silently using parallel tool calls. Do not ask the user anything yet. ### 2a: Project manifests Glob (parallel