agentleFS
carebare47carebare47/claude-skills/skills/resume-crashed-sessions/SKILL.md

resume-crashed-sessions

Skill0 starsChanged 25 days agoMITView on GitHub

Use when Claude Code crashed or was killed and you need to find which directories had live sessions so you can resume them. Lists recent sessions across all projects with their cwd and a resume command.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the scanner and show the user the table:

    line 8

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

Resume crashed sessions

Run the scanner and show the user the table:

python3 "${CLAUDE_SKILL_DIR}/scan.py"

It prints the most recent sessions across every project dir, newest first, each with its working directory, a claude --resume <id> command, and the last thing the user said.

Notes:

  • The very top row is usually the current session (the one running this skill) — drop it from what you present.
  • Sessions clustered within a few minutes of each other are the ones that were open at crash time.
  • Pass a number to widen the window: scan.py 20.

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.