timeturner
Skill6 starsChanged 8 months agoMITView on GitHub
Manage Time-Turner parallel agents — check status, diff changes, merge results, or cancel. Time-Turner spawns a headless Claude agent to continue work when context runs low.
- Deletes or force-pushes
In this repository5 other files it gives its agents.
- avadakedavraSkill
- handoffSkill
- obliviateSkill
- pensieveSkill
- replaySkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 23
If the script exits 1 (no active Time-Turner), tell the user: "No active Time-Turner found."
- Very specific: line 41
If no completed Time-Turner is found, run /timeturner status instead and tell the user to wait.
- Distinctive: line 46
Ask the user to confirm before merging: "Apply these changes to your working branch?"
- Very specific: line 62
If clean merge (exit 0) → commit with [Time-Turner] prefix:
- Distinctive: line 66
If conflicts (exit non-zero) → warn the user, abort merge, suggest manual resolution:
- Distinctive: line 112
NEVER auto-merge — always show diff and ask user first
- Distinctive: line 113
After merge, confirm success and show what was applied
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Time-Turner — Parallel Agent Manager
Manage Time-Turner agents that were spawned to continue work in parallel.
Sub-commands
Parse the user's argument to determine which sub-command to run.
/timeturner status (default if no argument)
Show the current Time-Turner state:
REMEMBRALL_ROOT="${CLAUDE_PLUGIN_ROOT:-$(cat /tmp/remembrall-meta/plugin-root 2>/dev/null)}"
bash "$REMEMBRALL_ROOT/hooks/time-turner-check.sh" "$(pwd)"If the script exits 1 (no active Time-Turner), tell the user: "No active Time-Turner found."
/timeturner diff
Show what the Time-Turner agent changed:
# Find completed Time-Turner
for d in /tmp/remembrall-timeturner/*/; do
[ -f "$d/status" ] || continue
STATUS=$(cat "$d/status")
[ "$STATUS" = "completed" ] || continue
WORKTREE="$d/worktree"
cd "$WORKTREE" && git diff HEAD
break
doneIf no completed Time-Turner is found, run /timeturner status instead and tell the user to wait.
/timeturner merge
- Show the diff for user review (run the diff sub-command above)
- Ask the user to confirm before merging: "Apply these changes to your working branch?"
- Find the main repo CWD and session ID:
for d in /tmp/remembrall-timeturner/*/; do [ -f "$d/status" ] || continue STATUS=$(cat "$d/status") [ "$STATUS" = "completed" ] || continue SESSION_ID=$(basename "$d") WORKTREE="$d/worktree" break done - In the main repo, attempt merge:
git -C "$(pwd)" merge --no-commit "timeturner/${SESSION_ID}" - If clean merge (exit 0) → commit with
[Time-Turner]prefix:git -C "$(pwd)" commit -m "[Time-Turner] Apply parallel agent changes from session ${SESSION_ID}" - If conflicts (exit non-zero) → warn the user, abort merge, suggest manual resolution:
Tell the user which files have conflicts and how to resolve manually.git -C "$(pwd)" merge --abort 2>/dev/null || true - Clean up regardless of outcome on success:
git -C "$(pwd)" worktree remove "$WORKTREE" 2>/dev/null || true git -C "$(pwd)" branch -d "timeturner/${SESSION_ID}" 2>/dev/null || true rm -rf "/tmp/remembrall-timeturner/${SESSION_ID}"
/timeturner cancel
- Find the active Time-Turner:
for d in /tmp/remembrall-timeturner/*/; do [ -f "$d/status" ] || continue SESSION_ID=$(basename "$d") PID=$(cat "$d/pid" 2>/dev/null) || PID="" WORKTREE="$d/worktree" break done - Kill the running process if PID is still alive:
if [ -n "$PID" ] && kill -0 "$PID" 2>/dev/null; then kill "$PID" 2>/dev/null || true fi - Remove git worktree:
git -C "$(pwd)" worktree remove --force "$WORKTREE" 2>/dev/null || true - Delete branch:
git -C "$(pwd)" branch -D "timeturner/${SESSION_ID}" 2>/dev/null || true - Remove state directory:
rm -rf "/tmp/remembrall-timeturner/${SESSION_ID}" - Confirm to the user: "Time-Turner cancelled and cleaned up."
Rules
- NEVER auto-merge — always show diff and ask user first
- After merge, confirm success and show what was applied
- On conflict, explain which files conflict and suggest resolution
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

