Menu
Rebuild eforge from source and restart the daemon. Use during development after making code changes so the MCP tools pick up the latest build.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Enqueue a source for the eforge daemon to build — PRD file, inline description, or conversation context. Use when the user wants to hand work off to eforge.
Initialize or edit eforge/config.yaml team-wide settings, with validation via daemon tools
Author eforge TypeScript extensions from a natural-language request using the existing extension tooling and docs/examples
Inspect the recovery verdict for a failed PRD and apply the recommended action (retry, continue-repair, abandon, or manual)
Create a new agent runtime profile in eforge/profiles/
List, inspect, and switch agent runtime profiles
| name | eforge-daemon-restart |
| description | Rebuild eforge from source and restart the daemon. Use during development after making code changes so the MCP tools pick up the latest build. |
Rebuilds eforge from source and restarts the persistent daemon so MCP tools serve fresh code.
Prerequisite: Must be run from the eforge project root with pnpm available.
Run a full build to pick up source changes:
pnpm build
On build failure: Stop immediately. Show the build error. Do not continue.
Stop the running daemon (if any):
eforge daemon stop
If the daemon wasn't running, that's fine — continue to Step 3.
Start a fresh daemon with the newly built code:
eforge daemon start
On failure: Show the error and suggest running eforge daemon start manually to diagnose.
Report that the daemon is running with fresh code. Include the port and PID from the output.