git-workflow

# Git Workflow ## Core Rules - Use a worktree for all substantive changes — never work directly in the main worktree - Worktrees are always created for the **outermost superproject**, never a submodule (Step 1 resolves this) - **Initialize** every new worktree with its mise init task (Step 2d), and **end** every worktree with full coverage — land the branch (plus any submodule work and pointer updates), then remove it (Step 4) - Use `merge` (not PRs) to land changes: `mise x -- mise run merge:develop` or `mise x -- mise run merge:main` - Never push without explicit user request — always ask after a successful commit - Check `no-commit-to-branch` hook in `.config/pre-commit-config.yaml` before committing to any branch ## Caller Preferences This command takes **no arguments** — callers parameterize its behavior through **declared preferences in the invocation text** (e.g. `/vwf:execute`: "isolate without asking; commit only — never merge/push"). Honor any such declared preference: it drives the **Step 1** consent (skip the worktree prompt when isolation is pre-declared) and the **Step 4** post-commit choice (take the declared action, skip the prompt). Absent a declared preference, ask as each step specifies. ## Safety Rules **Never:** - `--force`, `--no-verify`, `reset --hard`, force-push to `main`/`develop` - Update git config - Any destructive operation without explicit user request If hooks fail during a commit: fix the issue, then create a **new commit...