agentleFS
cukascukas/remembrall/skills/timeturner/SKILL.md

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

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
  1. Distinctive:

    If the script exits 1 (no active Time-Turner), tell the user: "No active Time-Turner found."

    line 23
  2. Very specific:

    If no completed Time-Turner is found, run /timeturner status instead and tell the user to wait.

    line 41
  3. Distinctive:

    Ask the user to confirm before merging: "Apply these changes to your working branch?"

    line 46
  4. Very specific:

    If clean merge (exit 0) → commit with [Time-Turner] prefix:

    line 62
  5. Distinctive:

    If conflicts (exit non-zero) → warn the user, abort merge, suggest manual resolution:

    line 66
  6. Distinctive:

    NEVER auto-merge — always show diff and ask user first

    line 112
  7. Distinctive:

    After merge, confirm success and show what was applied

    line 113

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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
done

If no completed Time-Turner is found, run /timeturner status instead and tell the user to wait.

/timeturner merge

  1. Show the diff for user review (run the diff sub-command above)
  2. Ask the user to confirm before merging: "Apply these changes to your working branch?"
  3. 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
  4. In the main repo, attempt merge:
    git -C "$(pwd)" merge --no-commit "timeturner/${SESSION_ID}"
  5. 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}"
  6. If conflicts (exit non-zero) → warn the user, abort merge, suggest manual resolution:
    git -C "$(pwd)" merge --abort 2>/dev/null || true
    Tell the user which files have conflicts and how to resolve manually.
  7. 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

  1. 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
  2. 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
  3. Remove git worktree:
    git -C "$(pwd)" worktree remove --force "$WORKTREE" 2>/dev/null || true
  4. Delete branch:
    git -C "$(pwd)" branch -D "timeturner/${SESSION_ID}" 2>/dev/null || true
  5. Remove state directory:
    rm -rf "/tmp/remembrall-timeturner/${SESSION_ID}"
  6. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.