configs/claude-code/skills/session-migrate/SKILL.md
Migrate a Claude Code session from another project folder to the current directory so claude --resume picks it up.
npx skillsauth add jimweller/dotfiles session-migrateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
STARTER_CHARACTER = 🚚
Migrate a conversation from another project to the current working directory.
--global (always global since migration implies cross-folder). Pass the user's keyword argument if provided. Multiple words are automatically OR-matched.~/.claude/skills/session-resume/scripts/claude-search-resume --global
~/.claude/skills/session-resume/scripts/claude-search-resume "keyword" --global
Filter & Display — From the search results, discard any sessions whose project path matches the current working directory (these are already local and can't be migrated). Also discard the current active session. Show only the remaining results to the user. If only one foreign session remains, auto-select it. If multiple remain, ask the user which one to migrate (by number or session ID). If none remain, tell the user no migratable sessions were found.
Migrate — Run the migrate script with the chosen session ID:
~/.claude/skills/session-migrate/scripts/claude-migrate-session --session-id <uuid>
claude --resume <new-id> command. Tell the user to quit this session and run that exact --resume command. Do NOT suggest --continue — the current session will be newer and --continue would pick it up instead of the migrated one..jsonl file and any subagents directorytesting
Search saved session transcripts for past decisions, actions, errors, and context that has left the current conversation window.
data-ai
Review a PRD for defects via Claude opus subagent.
development
Markdown authoring guidelines for formatting, code blocks, and structure. Use when writing or editing markdown files.
development
--- name: md-style description: README style guide for concise, direct documentation. Use when writing or editing README files. ß--- <!-- markdownlint-disable-file MD041 --> # README Style Guide Write concise, direct README files for experienced engineers. ## Principles - **No fluff** - Skip tables of contents, verbose explanations, development history - **No roadmaps** - Document current state only, not plans or decisions. Readme is an engineering specification. Not a project plan or chan