dw-checklisted

# dw-check — a fast look, then fixes **This is the review step, and it is repeatable mid-build.** Run it twice while the diff is small; `dw-land`'s closing verdict stays a thin last look and never grows a reviewer of its own. ## What it reads The diff against the default branch — both the branch and **the ref of it** resolved the way `dw-git` does, never `origin/` by reflex; `<base>` below is that ref. Plus the change's `CHANGE.md` for the goal, found by branch the same way `dw-next` finds it. `$ARGUMENTS` is read two ways, and this is the one skill in the catalog that mixes them: the single word **`codex`** switches mode (step 2), and anything else — including whatever follows that word — narrows the focus to a path or a topic. It writes **no `.ai/` artifact** — approved fixes land as code commits, and a gate you re-run freely doesn't need a report file rotting between runs. ## Workflow ### 1. Establish the diff `git diff <base>...HEAD` plus `git log --oneline <base>..HEAD`, narrowed by the focus part of `$ARGUMENTS` when given — `codex` is a mode, never a path. Read the `CHANGE.md` goal so findings are judged against what the change is trying to do, not against taste. ### 2. Delegate only when asked for it **Bare does not delegate, and does not nag.** Go straight to step 3. The `argument-hint` already advertises the option at the moment of typing, so a bare run that lobbies for a second opinion just taxes the cheap path. **On `codex`**, hand the same diff to the `