eforge-restart

Restart the eforge daemon after checking for active builds.

69|4|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/eforge-build/eforge --skill eforge-restart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eforge-restart
Source: https://github.com/eforge-build/eforge/tree/main/packages/pi-eforge/skills/eforge-restart
Command: npx skills add https://github.com/eforge-build/eforge --skill eforge-restart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely restarting the eforge daemon can be disruptive if builds are in progress. This Skill ensures a graceful stop, verification of active builds, and a clean restart to minimize disruption.

Core Features & Use Cases

  • Safe restart workflow that checks for active builds before stopping.
  • Step-by-step guidance for running the restart, plus a force-restart option when required.
  • Clear error handling and user feedback for scenarios where a restart cannot proceed.

Quick Start

Invoke the /eforge:restart command to safely restart the eforge daemon, ensuring no builds are running.

Frequently Asked Questions about eforge-restart

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

FAQPage Schema
How do I safely restart the eforge daemon without interrupting active builds?

To safely restart the eforge daemon, the system checks for active builds before stopping and starting a new instance, ensuring a graceful stop to minimize disruption. This workflow verifies build status before proceeding.

Can I force restart the eforge daemon if builds are currently in progress?

Yes, you can use a force-restart option to stop the eforge daemon even when active builds are detected in the environment. This overrides the standard safety guardrails when a immediate shutdown is required.

What happens if an error occurs during the eforge daemon restart process?

The eforge daemon restart process handles errors gracefully by providing clear user feedback when a restart cannot proceed. This ensures you are notified of safety guardrail failures or active build conflicts preventing the shutdown.

Why should I verify active builds before stopping a build daemon?

Verifying active builds before stopping a daemon prevents the disruption and potential corruption of in-progress compilation tasks. This safety check enforces guardrails to ensure a clean restart without losing build state.

How do I check the eforge daemon status before performing a restart?

The eforge restart workflow includes step-by-step guidance for checking active builds and verifying the daemon status before initiating a stop. This check is the core safety mechanism of the restart command.