Documentation
Nightshift command reference
Choose the right Nightshift command for setup, execution, status, quality work, diagnosis, stopping, and archiving.
Updated
Which Nightshift command should I use?
Use Setup once, Start for already-approved work, Hunt to compose catalog work, Quality to find applicable debt, Status for a read-only summary, Doctor for diagnosis, Stop for an immediate stop order, and Archive to rotate completed state.
Lifecycle commands
These commands operate the shift itself.
- Setup — scaffold private run state and propose gates.
- Start — one preflight, one verdict per line, then arm and work the punch list without asking.
- Status — every fact the helper resolved: items, parked decisions, snags, deadline, lease, and receipts.
- Doctor — inspect the workspace, rules, lease, and recovery state without repairing it.
- Stop — issue a stop-work order and leave unfinished items open.
- Archive — file completed history while keeping live state lean.
Work discovery
Use Hunt when you want catalog work selected or composed. Use Quality when you want applicable debt surveyed across tests, code, accessibility, contracts, documentation, dependencies, and security.
- Guided: choose one or more shifts.
- Automatic: your sentence is the objective, and Nightshift composes the entries that serve it.
- Review first: inspect the order before arming.
- Run directly: authorize immediate execution.
Supporting commands
Import Issues stages only explicitly named GitHub issues; it never searches and never writes back. Schedule generates a launch configuration but registers nothing by itself. Every helper runs through one dispatcher, ns, which resolves the host and the workspace; native Windows runs ns.ps1 with the same verbs, and the plugin ships no Python.
Start with a bounded prompt
This prompt names the outcome and preserves Nightshift’s review boundary. Paste it into the supported coding host from the project you want to change.
Show me the Nightshift commands and recommend the one that matches what I want to do, without starting anything yet.What this workflow does not claim
- Natural-language invocation is used in Codex; Claude Code exposes namespaced slash commands.
- External publication, merging, and deployment still require explicit authority.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.