sg-visual-review-stop

Stop a ShipGuard visual review HTTP server using build-review.mjs and fallback port kill.

7|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/bacoco/ShipGuard --skill sg-visual-review-stop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sg-visual-review-stop
Source: https://github.com/bacoco/ShipGuard/tree/main/plugins/shipguard/skills/sg-visual-review-stop
Command: npx skills add https://github.com/bacoco/ShipGuard --skill sg-visual-review-stop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stops a running Visual review HTTP server for a ShipGuard visual-tests run to avoid orphaned processes, free the review port, and provide clear status reporting.

Core Features & Use Cases

  • Graceful stop: Runs the project's visual-tests/build-review.mjs with --stop to shut down the review server cleanly.
  • Fallback process kill: If the primary stop fails or the PID is invalid, reads the port from visual-tests/_results/.server.pid (or defaults to 8888) and kills the process on that port using lsof and kill.
  • User-friendly feedback: Reports "No server running." when no PID file exists and prints a warning when the fallback kill-by-port method is used.

Quick Start

Stop the visual review HTTP server for the current project.

Frequently Asked Questions about sg-visual-review-stop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop a visual review server for a ShipGuard project?

To stop a visual review server for a ShipGuard project, invoke the visual-tests/build-review.mjs script with the --stop flag to gracefully shut down the running HTTP server and free the review port.

What should I do if the visual review server PID file is missing or invalid?

If the visual review server PID file is missing or invalid, the process falls back to reading the port from visual-tests/_results/.server.pid (defaulting to 8888) and terminates the process using lsof and kill.

Why do I have orphaned processes after running visual-tests?

Orphaned processes after running visual-tests occur when the visual review HTTP server is not terminated gracefully; stopping the server cleanly prevents these orphaned processes and frees the review port.

Can I stop the visual review server in a CI environment?

Yes, you can stop the visual review server in a CI environment; the stop mechanism applies to both local development and CI scenarios to ensure review servers are properly terminated and ports are freed.

What happens if no visual review server is running when I try to stop it?

If no visual review server is running when you attempt to stop it, the system checks for the PID file and reports "No server running." to provide clear status feedback without executing fallback kill commands.