nightwatch-initlisted

# Set a repo up for Nightwatch `init.mjs` does every step idempotently — preflight, the clone, the trust entry, the check command, the state directory, the kill switch, a dry run — and stops at the first thing it cannot do without you. This skill reads its report, asks one question, then runs it. Announce: "Using nightwatch-init to set this repo up for Nightwatch." Resolve the plugin path as `${CLAUDE_PLUGIN_ROOT}` when set, else this file's `../../nightwatch/` relative to its own location, and call the script with `node`. ## 1. Report first ``` node <plugin>/nightwatch/init.mjs --report ``` `--report` changes nothing — no clone, no trust entry, no state dir, no switch, no dry run — it only prints what each step would do. Show the status table. If the `check` step reports `needs you`, the repo has no `scripts/check` and no `--check-cmd` was given. Read `.github/workflows/*.yml` yourself as well as the candidates `--report` lists under "check-command candidates" (one `run:` line per CI step that looks like a check — fmt, lint, test, etc.); drop anything platform-only (a Windows- or container-only job) or that needs a secret this session doesn't have, and say which you dropped and why. The survivors become one `--check-cmd "<line>"` per flag, run in the order CI runs them. If the `switch` step reports `needs you`, the kill switch (`LANDING_STATE`) is unset or not `run`. Say the exact command: ``` gh variable set LANDING_STATE --body run ``` ## 2. Ask one question AskU