/SKILL.md
Manage background processes like dev servers. Use when you need to start, stop, or check status of long-running processes.
npx skillsauth add mayardh/bgproc bgprocInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A CLI for managing background processes. All commands output JSON to stdout.
Use bgproc when you need to:
# Start a process
bgproc start -n <name> -- <command...>
bgproc start -n devserver -- npm run dev
bgproc start -n devserver -t 300 -- npm run dev # auto-kill after 5 min
# Start and wait for port (recommended for dev servers)
bgproc start -n devserver -w -- npm run dev # wait for port, then exit
bgproc start -n devserver -w 30 -- npm run dev # wait up to 30s for port
# Force restart (kill existing process first)
bgproc start -n devserver -f -w -- npm run dev
# Check status (returns JSON with pid, running state, port)
bgproc status <name>
# View logs
bgproc logs <name>
bgproc logs <name> --tail 50
bgproc logs <name> --errors # stderr only
# List all processes
bgproc list
bgproc list --cwd # filter to current directory
# Stop a process
bgproc stop <name>
bgproc stop <name> --force # SIGKILL
# Clean up dead processes
bgproc clean <name>
bgproc clean --all
bgproc start -n devserver -w -- npm run dev
-f to force restart if already runningbgproc logs devserverbgproc stop devserverlsof and checks child processes (macOS/Linux only)-w to wait for port detection before returning-f to force restart (kills existing process with same name)development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.