hyper-autopilotlisted

This skill should be used when the user asks to "autopilot", "autopilot now", "kick off autopilot immediately", "start work in N hours", "work on it while I'm asleep", "trigger in a few hours", "set up autopilot for later", or makes any "leave it running" / "fire-and-forget" request over the local hyperclaude loop (distinct from GitHub-native octoperator autopilot). Runs a fire-and-forget autonomous workflow that loops the hyperclaude cycle (hyper-auto → plan-loop → implement-loop) → ff merge → push → next task, until context exhausts or a stop condition fires. Two delivery modes — (a) **scheduled** wakes up N hours/minutes from now via `CronCreate`; (b) **immediate** starts right now in this session, no cron. Requires the hyperclaude plugin installed (it drives `/hyperclaude:hyper-auto`).
zeikar/dotfiles · ★ 1 · Code & Development · score 72

Install: claude install-skill zeikar/dotfiles

# Hyper-autopilot — autonomous-loop runner (scheduled or immediate) Thin driver over the **hyperclaude plugin**. Assemble a per-round loop prompt — `/hyperclaude:hyper-auto` → ff-merge to main → push → pick next task → repeat — and fire it now or on a schedule. `hyper-auto` owns the plan→implement chaining and its between-phase safety stop; autopilot only adds scheduling + merge/push/next-task orchestration on top. - **Prerequisite:** if hyperclaude is not installed there is nothing to drive — STOP and say so. Never hand-roll the plan/implement steps. - **Single round only** (no auto-pickup of the next task): skip this skill, run `/hyperclaude:hyper-auto` directly. Autopilot's value is the multi-round loop. - **Remote/cloud execution:** use `/schedule` (RemoteTrigger), not this. ## Modes - **Immediate** — "now" / "right away" / no time given: start executing the assembled prompt inline this session. - **Scheduled** — "in N hours" / "tomorrow 8am" / "at 03:00": fire once via `CronCreate`. The session must stay **alive and idle** until then (closing the terminal kills it; locking the laptop is fine). Ambiguous phrasing → ask which, don't guess. ## Procedure 1. **Inputs.** Round-1 task (one paragraph — `hyper-auto` expands it). Optional: follow-up candidates, extra constraints. 2. **(Scheduled only) Resolve time + build cron.** Read live time (`date -u +%Y-%m-%dT%H:%M:%SZ`, `date +%Y-%m-%d`) — never a stale conversation anchor. Parse the user's "when" against it and echo