Vp long running processes
Reusable Agent Skills by VdustR
npx -y skills add VdustR/skills --skill vp-long-running-processesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Manage long-running processes safely: find reusable instances before starting new ones and decide carefully before stopping anything. Use when about to start a dev server, watcher, preview server, browser session, or background agent; when a port is already in use or EADDRINUSE appears; when checking whether a server is already running; or when asked to stop, kill, or restart a process. Boundary: not for one-shot commands that exit on their own.
SKILL.md
2.1 KB, as published. Nobody here has run it
Long-Running Processes
Reuse before spawning; confirm before killing.
Find Existing Instances
Find processes by project path instead of guessing ports. On macOS, use full-width process output so long commands are not truncated:
ps -ewwo pid,args 2>/dev/null | grep -F "$(pwd)" | grep -v grep
Substitute another project's path for $(pwd) when checking a different
project. Processes started with a relative path (e.g. npm run dev) may not
show the project path in their arguments — also search by process or script
name before concluding nothing is running.
If a matching process is found, inspect its listening ports:
lsof -nP -a -p <PID> -iTCP -sTCP:LISTEN
Keep -a: lsof ORs its selection options by default, so without it the
command lists every listening socket on the machine, not just the target
PID's.
Detection Rules
- Use port-based detection only when the port is read from config or process output, not guessed.
- For watchers that do not listen on a port, search by process name and project path.
- For browser sessions, check existing pages or tabs before opening a new one when the platform exposes browser state.
- For background agents or asynchronous jobs, check whether related work is already running before starting another instance.
Stopping And Restarting
- Do not stop, kill, or restart a long-running process without user confirmation unless the user explicitly requested shutdown or restart.
- If an existing process belongs to another project, report its command, path, and port (if known) before deciding what to do.