homelab-reboot

Record reboot intent to ~/agent-state/pending.md before executing sudo systemctl reboot.

Updated Feb 9, 2025
One-click install
npx skills add https://github.com/carter2099/.dotfiles-homelab --skill homelab-reboot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: homelab-reboot
Source: https://github.com/carter2099/.dotfiles-homelab/tree/main/.claude/skills/homelab-reboot
Command: npx skills add https://github.com/carter2099/.dotfiles-homelab --skill homelab-reboot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reboot the homelab host safely by recording the reboot intent and in-flight work to ~/agent-state/pending.md before performing the reboot, ensuring the next session can resume with proper context.

Core Features & Use Cases

  • Safely initiates a reboot by generating a structured pending state that documents the reason and in-flight work.
  • Requires explicit user confirmation prior to reboot to prevent unintended downtime.
  • Provides a deterministic reboot path using systemd, preserving context for the next session.

Quick Start

Initiate a safe reboot by providing a reason; the agent will summarize in-flight work, create ~/agent-state/pending.md, prompt for confirmation, and then reboot if confirmed.

Frequently Asked Questions about homelab-reboot

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

FAQPage Schema
How do I safely reboot a homelab host without losing my current work context?

A safe homelab reboot requires recording your reboot intent and in-flight work to a pending state file before restarting. This ensures the next session can resume exactly where you left off.

What is a context-preserving reboot and how does it work?

A context-preserving reboot works by generating a structured state file that documents the reboot reason and pending tasks before executing the restart. This mechanism allows your agent to recover its previous state after the machine comes back online.

How do I execute a systemd reboot while saving in-flight agent tasks?

You can execute a systemd reboot while saving in-flight tasks by first summarizing your active work into a dedicated pending state file. The system then prompts for explicit user confirmation before running the restart command.

Does a safe homelab reboot require explicit user confirmation?

Yes, a safe homelab reboot requires explicit user confirmation prior to executing the restart. This prevents unintended downtime and ensures you have validated the pending state being saved.

When should I use a pending state file for homelab maintenance restarts?

You should use a pending state file for homelab maintenance restarts whenever you are applying updates, fixing failures, or performing any action requiring a restart. It guarantees your agent's in-flight work is not lost during the downtime.