resume-from-chat-history

Resume from chat history

Rebuild the context of a broken or lost Kiro chat from the auto-saved session files on disk, then hand off cleanly so work continues without losing decisions or the mid-task position.

Background: where Kiro keeps chat history

Kiro CLI auto-saves every conversation turn to per-directory session files under:

~/.kiro/sessions/cli/
├── {session_id}.json     # metadata: cwd, title, created_at, updated_at, session_state
├── {session_id}.jsonl    # append-only conversation log (one JSON object per line)
├── {session_id}.history  # prompt history
└── {session_id}.lock     # present ONLY while that session is actively running

Key facts this skill relies on:

• Sessions are keyed by working directory (cwd field in the .json).
• The currently running session has a .lock file; a broken/ended one does not (a stale lock can remain after a crash, so also use updated_at and cwd to disambiguate).
• The .jsonl log holds the real content. Each line is one JSON object with a kind field:
  • kind: "Prompt" → a user message. Text lives in data.content[] items where kind == "text" (field data).
  • kind: "AssistantMessage" → an assistant message (its data.content may be a plain string or a list).
  • kind: "ToolResults" → tool outputs (usually skip when reconstructing intent).
• There is no built-in content search; use rg over the .jsonl files.

When to use

• The user reports the previous chat broke or was lost: "壊れた", "落ちた", "また壊れた", "the chat broke".
• The user asks to hand off / resume: "引き継いで", "続きから", "内容読んで引き継げる", "resume the prior work".
• The current session clearly lacks context for work already in progress — e.g. a feature branch is checked out with many uncommitted changes, but nothing in this session explains them.

If the user instead wants to re-run a stalled tool call inside the same live session, that is the next skill, not this one.

Workflow

1. Establish the current working directory and in-progress work