菜单
Safely restart the local PwrAgent Electron development app after pulling, rebasing, or merging changes. Use when Codex is running inside or alongside the PwrAgent dev app and a normal restart could kill the current session before `pnpm dev` is relaunched.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Prepare, validate, tag, publish, and monitor guarded PwrAgent desktop releases. Use when the user asks to release PwrAgent, prepare a vX.Y.Z or vX.Y.Z-prerelease tag, update release notes or CHANGELOG.md for a desktop release, verify package.json/tag/changelog alignment, trigger the macOS signed/notarized release workflow, or inspect release workflow status.
Check and summarize PwrAgent GitHub Release asset download statistics. Use when the user asks for download counts, bytes served, DMG or ZIP stats, updater ZIP traffic, per-release stats such as beta.22/beta.21/beta.20, or whether GitHub release downloads show any traffic.
Start, stop, restart, and verify the local PwrAgent Electron development app with `PWRAGENT_PROFILE=dev` from the current checkout. Use when Codex needs to close any running dev-profile PwrAgent instance, launch `pnpm dev` in the current working directory, or confirm the dev-profile app came up.
Record, export, derive, and refresh desktop replay-backed E2E fixtures for PwrAgent. Use when Codex needs to seed or update `apps/desktop/e2e/fixtures/*` from a live desktop session with Computer Use, add a new capture recipe, promote `raw.capture.jsonl` into `replay.fixture.json`, or wire a replay-backed Electron spec around a captured scenario.
| name | pwragent-dev-restart |
| description | Safely restart the local PwrAgent Electron development app after pulling, rebasing, or merging changes. Use when Codex is running inside or alongside the PwrAgent dev app and a normal restart could kill the current session before `pnpm dev` is relaunched. |
Use this skill when the running Electron app must be stopped and restarted from a freshly updated checkout, especially after merging a PR into ~/github/PwrAgnt.
Confirm the target checkout is updated and clean enough to run:
git -C /Users/huntharo/github/PwrAgnt status --short --branch
git -C /Users/huntharo/github/PwrAgnt log -1 --oneline --decorate
Dry-run the restart to see which processes would be stopped:
.agents/skills/pwragent-dev-restart/scripts/restart-pwragent-dev.zsh \
schedule --root /Users/huntharo/github/PwrAgnt --delay 30 --dry-run
Schedule the restart and answer the user before the delay expires:
.agents/skills/pwragent-dev-restart/scripts/restart-pwragent-dev.zsh \
schedule --root /Users/huntharo/github/PwrAgnt --delay 30
After the delay, verify the app came back:
tail -120 /Users/huntharo/github/PwrAgnt/.local/pwragent-dev-restart.log
pgrep -fl '/Users/huntharo/github/PwrAgnt|PwrAgent|pnpm.*dev|electron-vite'
pnpm dev:dev from the checkout.--detach-start, the script starts the dev command in a detached tmux session when tmux is available. This survives parent command cleanup while keeping the dev logs in the configured restart log.nohup sleep wrapper for the delayed timer. Do not use launchctl submit here: launchd can keep descendant pnpm dev processes in the submitted job context and relaunch them after they exit./Users/huntharo/github/PwrAgnt.<root>/.local/pwragent-dev-restart.log.--dry-run before scheduling unless the user explicitly asks to restart immediately.