stop — Claude Code skill: what it does, how to install
A Claude Code skill pauses a Nightshift session while keeping unfinished items open. It runs when the session needs to stop immediately.
MIT ★ 571 updated 2026-11-16
npx skills add orwa-mahmoud/nightshift --skill stop -a claude-codeWhat stop does
The skill calls stop-shift to pause the project session and record the stop reason with a UTC timestamp. The helper adds a line to the shift log and terminates only a verified live Nightshift watchman. It also reports the count of open items.
The deadline, punch list, and other work files remain on disk; open items stay open. The helper writes the stop marker itself. A manual touch marker takes effect only at the next Stop event or watchman wake, so it does not disarm the session immediately. The command is "$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" stop-shift; native Windows uses the ns.ps1 script in PowerShell.
What it helps with
- pause an active Nightshift session
- keep unfinished work items open
- preserve the deadline when stopping
- record the stop in the shift log
Example prompts for the agent
- Stop the current Nightshift session and leave unfinished items open.
- Pause the shift now, preserve its deadline, and report the open-item count.
- Stop Nightshift safely without closing the punch list.
How to install stop
1Skills CLI (Vercel)
npx skills add orwa-mahmoud/nightshift --skill stop -a claude-code2Manually: put the files in place
~/.claude/skills/stop/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/stop/
1Skills CLI (Vercel)
npx skills add orwa-mahmoud/nightshift --skill stop -a codex2Manually: put the files in place
.agents/skills/stop/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add orwa-mahmoud/nightshift --skill stop -a cursor2Manually: put the files in place
.cursor/skills/stop/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install orwa-mahmoud/nightshift plugins/nightshift/skills/stop2Manually: put the files in place
.github/skills/stop/SKILL.md1Skills CLI (Vercel)
npx skills add orwa-mahmoud/nightshift --skill stop -a gemini-cli2Platform CLI
gemini skills install https://github.com/orwa-mahmoud/nightshift --path plugins/nightshift/skills/stopManually: put the files in place
.devin/skills/stop/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add orwa-mahmoud/nightshift --skill stop -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about stop
How do I install stop in Claude Code?
Run npx skills add orwa-mahmoud/nightshift --skill stop -a claude-code. The skill file is installed at ~/.claude/skills/stop/SKILL.md.
What does the stop skill do?
It pauses a Nightshift session, records the stop reason and time, and keeps open items and the deadline on disk.
How do I resume a session after using stop?
In Claude Code, run /nightshift:start. Start clears the pause markers and begins a new ownership lease.
Source text
SKILL.md · MIT
---
name: stop
description: Issue a stop-work order that pauses the shift now and leaves unfinished items open.
license: MIT
metadata:
internal: true
---
Pause the host-opened project immediately so the owner can edit the punch list and resume later.
Resolve the installed plugin root to an absolute `$NIGHTSHIFT_PLUGIN_ROOT` — `${CLAUDE_PLUGIN_ROOT}`
on Claude Code, `$PLUGIN_ROOT` on Codex when set, otherwise the absolute path this skill was
attached from (`skills/stop/SKILL.md`). Run every command below through
`"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns"` — native Windows: `& "$NIGHTSHIFT_PLUGIN_ROOT\runtime\windows\ns.ps1"`
in the PowerShell tool, same verbs — which resolves the host and the workspace; `ns help` lists the
verbs, and `ns bind` prints the six resolved facts (`TASK_ROOT`, `NIGHTSHIFT_WORKSPACE`, `NS`,
`NIGHTSHIFT_PLUGIN_ROOT`, `HOST`, `SOURCE`); `$NS` below is that `NS`. Never a bare relative path: the working
directory persists between calls. Each `$NS/...` path below is where the current layout keeps that file;
`ns path <key>` prints where this workspace keeps it, and `ns path --list` names every key.
Run the trusted helper. Do not write `$NS/STOP` by hand, do not delete `$NS/run/.shift-armed`, and do
not kill `$NS/run/.watchman` yourself — the helper performs the safe teardown:
```bash
"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" stop-shift
```
The helper writes `$NS/STOP` with a reason and UTC timestamp, appends `stopped by owner` to
`$NS/run/shift-log.md`, and kills only a verified live Nightshift watchman. It does not remove
`$NS/run/.shift-armed`. It drops `$NS/run/.shift-session` so the same conversation is not a second
agent on the next Start. Open boxes stay open as the record. Hardhat stays until clock-out writes
`$NS/run/.ended`. Reset is the manual escape. The deadline, punch list, rules, parking lot, work
orders, receipts, archives, research, opportunities, and shift history stay on disk. Do not wait
for a later Stop event to write the marker — the helper writes it now.
Report the helper's `open-items` count and that the deadline was preserved. A second Stop is safe.
Resume later with Start (`/nightshift:start` on Claude Code, or ask Nightshift to start on Codex).
Start clears the pause markers and begins a new ownership lease. A future preserved deadline
remains the deadline. An expired preserved deadline is not silently renewed: write a new UNIX epoch
to `$NS/run/deadline`, or run Reset then Start.
This works from the bound conversation, from a helper conversation, and when a failed clock-out left a recovery nonce that still fences the recorded conversation.
**Panic form (does not disarm immediately):** from any POSIX terminal,
`touch "$NS/STOP"`. In native Windows PowerShell, run
`New-Item -ItemType File -Force "$NS\STOP"`. That marker is honored at the next Stop event or
watchman wake. Prefer the helper when the model is stuck — it does not wait for that event.
© orwa-mahmoud · MIT · orwa-mahmoud/nightshift