メニュー
Use when the ShipGuard review dashboard server should be shut down after a review session — stops the sg-visual-review HTTP server via its PID file, with a port-based fallback.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Lock the literal user mission and authorization level before work to prevent scope drift, inferred permission, adjacent-work expansion, plan churn, and false completion. Use unconditionally when the active model is gpt-5.6 or gpt-5.6-sol at any reasoning effort, when the user names GPT-5.6 Sol or Sol Ultra as the agent, after terse continuations such as continue/do all, after compaction or correction, and whenever review/plan/code/publish/live boundaries could be crossed.
Use when UI changes need visual verification — after an audit or process check flags routes, after frontend edits, or on demand to run or re-run the project's visual test manifests.
Use when a change is ready to ship — before a PR or release — and the user wants the full ShipGuard verification (audit, behavior, visual, review) run on it.
Use when a project needs visual test manifests created or refreshed — before the first visual run, after UI routes change, or when sg-visual-run reports uncovered routes.
Use after visual runs, code audits, or process checks when results need human review — builds and serves the interactive ShipGuard dashboard.
Use after visual runs, screenshot capture, frontend PRs, or before stakeholder review — creates the durable ShipGuard before/after report for UI-visible changes.
| name | sg-visual-review-stop |
| description | Use when the ShipGuard review dashboard server should be shut down after a review session — stops the sg-visual-review HTTP server via its PID file, with a port-based fallback. |
| context | conversation |
Stop the review page HTTP server.
node visual-tests/build-review.mjs --stop
--stop short-circuits: it only reads visual-tests/_results/.server.pid, kills that process, and removes the PID file — no rebuild, no config parsing.
If no PID file exists, report "No server running."
CLI equivalent: node visual-tests/shipguard.mjs stop --all — stops the app-under-test server (started by shipguard serve/run) AND the review server in one command.
If --stop exits with a non-zero code, fall back to killing by port. The PID file contains two lines: <pid> then <port>.
# Read the port from line 2 of the PID file; default to 8888 if missing
port=$(sed -n '2p' visual-tests/_results/.server.pid 2>/dev/null)
[ -z "$port" ] && port=8888
lsof -ti:"$port" | xargs -r kill
Print a warning if fallback was needed: "Warning: --stop failed, used lsof fallback to kill process on port {port}."