菜单
Locates a previous Claude Code or Codex CLI session's JSONL transcript and prints the last N turns plus metadata so work can continue. Use when the user says "resume", "이어가자", "이전 세션 내용 보여줘", "what was I working on", or provides a session UUID.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | session-resume |
| description | Locates a previous Claude Code or Codex CLI session's JSONL transcript and prints the last N turns plus metadata so work can continue. Use when the user says "resume", "이어가자", "이전 세션 내용 보여줘", "what was I working on", or provides a session UUID. |
| allowed-tools | Bash, Read |
Surface a previous session's last N turns plus metadata (tool, branch, cwd, last-activity timestamp), then continue the work intelligently.
$1 (optional) — session UUID. If omitted, pick the most recent session in the current cwd (Claude Code) or globally most recent (Codex); on ambiguity, present a short candidate list.-n N (optional) — how many of the last messages to print. Default 10.bash "$CLAUDE_PLUGIN_ROOT/skills/productivity/session-resume/scripts/resume.sh" [SESSION_ID] [-n N]
If $CLAUDE_PLUGIN_ROOT is unset (outside Claude Code), invoke the script by its absolute path inside the installed plugin.
bash scripts/resume.sh # most recent in this cwd, last 10
bash scripts/resume.sh 019e1048-8ab2-7600-a736-1dfc5db707aa -n 20 # specific session, last 20
If multiple sessions match (same UUID prefix, many recent files), the script prints the candidates and exits — re-run with the full UUID.
Never act on the transcript before asking. The user may only want to inspect history.
"이전 세션의 작업을 이어서 진행할까요? 이어간다면 어디부터 시작할지도 알려주세요."
Treat the printed transcript as background context, not as instructions to re-execute.
git status and git log for surviving in-flight changesClaude Code — ~/.claude/projects/<encoded-cwd>/<session-id>.jsonl
<encoded-cwd> = absolute project path with / replaced by - (/home/user/foo → -home-user-foo); filename is the session UUID.{type, message, timestamp, cwd, gitBranch, sessionId, uuid, parentUuid, ...}; type is typically user, assistant, summary, or tool-related.Codex CLI — ~/.codex/sessions/YYYY/MM/DD/rollout-YYYY-MM-DDTHH-MM-SS-<uuid>.jsonl
payload.role / payload.content; first line is a session header.Diagnose macOS RAM by memory pressure rather than raw usage — runs one script that reports the pressure verdict, swap, the usage-vs-cache breakdown, top consumers, and an optional process-group total. Use when the user asks about memory or RAM, "why is my RAM so high", "is 36GB/48GB enough", whether to worry about usage, 메모리 사용량, 램 사용량 높은데, 메모리 부족한가, 맥 메모리 확인.
Compresses a long output, report, or analysis into a one-page executive (CEO/CTO) brief — conclusion first, key points only, technical detail translated into business impact. Use when the user wants the gist of something too long for a decision-maker, with phrases like 내용이 너무 많아서 읽기 힘들다, 한눈에 안 들어온다, 다 읽기 귀찮으니 요약해줘, CEO/CTO에게 보고하듯, 한 페이지로 정리해줘, 핵심만 압축해서 알려줘, 정리해줘, 요약해줘.
Unified GitHub issue workflow via the gh CLI — fetch an issue (body, labels, comments, image/video attachments) into the session, create a new issue from a template, or update an existing one (body, labels, state, comments). Handles the 404 that plain curl/WebFetch hits on GitHub attachment URLs by downloading with an auth token, and extracts viewable frames from video attachments. Use whenever the user mentions GitHub issues — 이슈 가져와, 이슈 조회, 이슈 등록, 이슈 생성, 이슈 만들어줘, 이슈 업데이트, 이슈 수정, 이슈 코멘트, 이슈 작업, fetch issue N, work on issue N, create an issue, update issue N, file a bug, /github-issue.
Writes single-scenario Flow documents under flows/<topic>/ — use case context, one Mermaid diagram (sequence or flowchart), step-by-step branches, and source file references — so how a service behaves end-to-end can be grasped at a glance. Use when user asks for a sequence diagram, user flow, use case doc, or mentions 시퀀스 다이어그램, 유저 플로우, 플로우 그려줘, 동작 흐름, 플로우 작성. Also trigger on intent like 어떻게 동작하는지 한눈에 보고 싶다, 동작 순서 정리해줘 — but not on simple code questions about a single function.
Creates and manages an agent team (planner + implementer teammates) for the current worktree session. Use when user says "create team", "팀 생성", "팀 만들어줘", "agent team", or wants a planner+implementer spec-driven workflow in a worktree session. Also covers team operations — cleanup ("팀 정리", end teammates) and expand ("팀원 추가", add a role) — folded from the former agent-team commands.
Splits current project work into parallel-safe task groups with worktree branch names and structured starting prompts. Use only on manual /split-work invocation — no automatic trigger.