Skill

hermit-hand-back

Summarizes operator takeover activity via git log, optionally queues instructions in NEXT-TASK.md, updates SHELL.md status, and restarts hermit Docker container after /hermit-takeover.

Git

Docker

npx claudepluginhub gtapps/claude-code-hermit --plugin claude-code-homeassistant-hermit

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Hand control back to the autonomous hermit after an operator takeover session. Summarizes what you did, optionally leaves instructions, and restarts the container.

SKILL.md

Similar Skills

hermit-takeover

Stops Docker container running autonomous hermit agent, marks session as operator takeover, loads full context from config and session files, and presents structured summary for interactive continuation.

claude-code-hermit

handoff

332

Generates structured session handoff Markdown documents summarizing accomplishments from git logs, file changes, research, plans, and issues. Captures pause points and key files for continuation. Use /handoff [topic].

1 file

agentops

session-handoff

955

Generates and validates handoff documents for transferring AI agent session context across pauses, context limits, milestones, or resumes. Captures git state and next steps.

11 files

session-handoff

Stats

Stars18

Forks2

Last CommitApr 14, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Hermit Hand-Back

Hand control back to the autonomous hermit after an operator takeover session. Summarizes what you did, optionally leaves instructions, and restarts the container.

Plan

1. Verify takeover state

Read .claude-code-hermit/sessions/SHELL.md and check for the **Takeover:** timestamp line.

If found: extract the takeover timestamp for use in step 2
If not found: warn "No takeover timestamp found in SHELL.md — proceeding anyway." Use a fallback of 24 hours ago for the git log.

2. Summarize operator activity

Build a summary of what happened during the takeover using git:

Run git log --oneline --since="<takeover_timestamp>" to get commits made during takeover
If there are commits: use the oldest commit's parent as the anchor — run git log --oneline --since="<takeover_timestamp>" --format="%H" | tail -1 to get the first takeover commit, then git diff --stat <first_commit>^..HEAD for a file change summary
Format as a concise summary:
- "3 commits during takeover: fixed auth bug, updated README, bumped version. 5 files changed."
- Or: "No commits during takeover." (operator may have just explored, tested, or reviewed)

3. Ask for instructions

Ask the operator: "Any instructions for the hermit to work on next?"

If yes: write the instructions to .claude-code-hermit/sessions/NEXT-TASK.md. This file is automatically picked up at the next session-start.
If no / skip: don't create or modify NEXT-TASK.md

4. Update SHELL.md

Add a progress log entry summarizing the takeover:

[HH:MM] Operator takeover — <git summary from step 2>. <Instructions queued / No specific instructions.>

Change **Status:** from operator_takeover to idle
Remove the **Takeover:** timestamp line

5. Restart the container

Run .claude-code-hermit/bin/hermit-docker up in the project root.

Check that the container started: run docker compose -f docker-compose.hermit.yml ps --status running after a few seconds.

If running: confirm success
If not running: warn "Container didn't start — check .claude-code-hermit/bin/hermit-docker logs for errors."

6. Confirm hand-back

Print confirmation:

Hermit is back online.
Takeover summary: <git summary>
Instructions: <queued / none>

Check status anytime: .claude-code-hermit/bin/hermit-status