Skill

history-insight

Analyzes Claude Code session history JSONL files to extract insights, summaries, and patterns from conversations. Processes current project or all sessions with bash, jq, and subagents.

Bash

developer-tools

npx claudepluginhub team-attention/plugins-for-claude-natives --plugin session-wrap

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Claude Code 세션 히스토리를 분석하고 인사이트를 추출합니다.

Supporting Assets

references/session-file-format.mdscripts/extract-session.sh

SKILL.md

Similar Skills

finishing-a-development-branch

174.6k

Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.

superpowers

systematic-debugging

174.6k

Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.

10 files

superpowers

writing-plans

174.6k

Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.

1 file

superpowers

Stats

Parent Repo Stars652

Parent Repo Forks80

Last CommitJan 14, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

History Insight

Claude Code 세션 히스토리를 분석하고 인사이트를 추출합니다.

Data Location

~/.claude/projects/<encoded-cwd>/*.jsonl

Path Encoding: /Users/foo/project → -Users-foo-project

상세 파일 포맷: ${baseDir}/references/session-file-format.md

Execution Algorithm

Step 1: Ask Scope [MANDATORY]

스코프 결정:

명시된 경우 (AskUserQuestion 생략 가능):
- "현재 프로젝트만" / "이 프로젝트" → current_project
- "모든 세션" / "전체" → all_sessions

명시되지 않은 경우 - AskUserQuestion 호출:

question: "세션 검색 범위를 선택하세요"
options:
  - "현재 프로젝트만" → ~/.claude/projects/<encoded-cwd>/*.jsonl
  - "모든 Claude Code 세션" → ~/.claude/projects/**/*.jsonl

Step 2: Find Session Files

# Current project only
find ~/.claude/projects/<encoded-cwd> -name "*.jsonl" -type f

# All sessions (모든 프로젝트)
find ~/.claude/projects -name "*.jsonl" -type f

날짜 필터링: 파일의 mtime(수정시간) 확인 후 필터. OS별 stat 옵션 다름:

macOS: stat -f "%Sm" -t "%Y-%m-%d" <file>
Linux: stat -c "%y" <file>

Step 3: Process Sessions

Decision Tree

Session files found?
├─ No → Error: "No sessions found"
└─ Yes → How many files?
    ├─ 1-3 files → Direct Read + parse
    └─ 4+ files → Batch Extract Pipeline

1-3 Files

직접 Read로 JSONL 파싱. 파일이 크면(≥5000 tokens) extract-session.sh 사용:

${baseDir}/scripts/extract-session.sh <session.jsonl>

4+ Files: Batch Extract Pipeline

캐시 디렉토리 생성 (/tmp/cc-cache/<analysis-name>/)
세션 목록 저장 (sessions.txt)
jq로 메시지 일괄 추출 (user_messages.txt)
정리 및 필터링 (clean_messages.txt)
Task(opus)로 종합 분석

파일이 너무 클 때: 병렬 배치 분석

clean_messages.txt가 너무 커서 Read 실패 시:

파일 분할:

split -l 2000 clean_messages.txt /tmp/cc-cache/<name>/batch_

병렬 Task(opus) 호출:

Task(subagent_type="general-purpose", model="opus", run_in_background=true)
prompt: "batch_XX 파일을 읽고 주제/패턴 요약해줘"

결과 병합: Task(opus)로 종합

Step 4: Report Results

## Session Capture Complete

- **Sessions:** N files processed
- **Messages:** X total, Y after filter

### Extracted Insights
[분석 결과]

Error Handling

Scenario	Response
No session files found	"No session files found for this project."
File too large	Auto-preprocess with extract-session.sh
jq not installed	"Error: jq is required. Install with: brew install jq"
Task failed	"Warning: Could not process [file]. Skipping."
0 relevant sessions	"No sessions matched your criteria."

Security Notes

출력에 전체 경로 노출 금지 (~ prefix 사용)

Related Resources

${baseDir}/scripts/extract-session.sh - JSONL 압축 (thinking, tool_use 제거)
${baseDir}/references/session-file-format.md - JSONL 구조 및 파싱