From session-improver
Analyze a Claude Code session and recommend improvements to reduce token waste, prevent linter loops, and automate repetitive workflows. Use when user says "improve session", "analyze session", "optimize session", or "/improve-session".
How this skill is triggered — by the user, by Claude, or both
Slash command
/session-improver:improve-sessionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze Claude Code session transcripts and generate actionable recommendations to reduce token waste, prevent linter loops, and automate repetitive workflows.
Analyze Claude Code session transcripts and generate actionable recommendations to reduce token waste, prevent linter loops, and automate repetitive workflows.
/improve-session — Analyze the most recent session/improve-session <session-id> — Analyze a specific past session/improve-session --current — Analyze the current live sessionRun the parser script to extract a structured summary:
ruby "${CLAUDE_SKILL_DIR}/scripts/parse-session.rb" <session-id-or-path>
If CLAUDE_SKILL_DIR is not set, fall back to the skill's location relative to this file. You can detect it by looking at the directory containing this SKILL.md.
The argument is either:
~/.claude/history.jsonl)--current for the most recent session.jsonl fileThe script outputs JSON with these sections:
linter_loops — Linter smells that triggered multiple edit cyclestool_failures — Tools that failed and were retriedrepeated_sequences — Workflow patterns that repeated 3+ timeslarge_reads — Files read 3+ times in the sessionhook_failures — Hooks that failed repeatedlypermission_events — Tools that needed human approvalFor each finding, read relevant project files to understand what's already configured:
CLAUDE.md (if the session had a project path).claude/settings.json and .claude/settings.local.json.claude/hooks/ directory.reek.yml, .rubocop.yml, eslint.config.*, etc.~/.claude/CLAUDE.md~/.claude/settings.jsonRead the reference files for patterns and templates (relative to this SKILL.md):
references/analyzers.md — What each finding type meansreferences/fix-templates.md — Templates for each fix typereferences/ruby-linter-patterns.md — Ruby-specific patternsFor each finding, generate a specific recommendation:
project CLAUDE.md — Rules specific to this repoglobal CLAUDE.md — Rules that apply everywhereproject settings.json — Hooks/permissions for this repoglobal settings.json — Hooks/permissions everywherehookify rule — Behavioral guardskill — Reusable workflowPresent findings in this format:
## Session Analysis: <session-id>
**Project:** <path>
**Duration:** X min | **Turns:** N | **Edits:** N | **Tool calls:** N
---
### Finding 1: <title> (N iterations)
**Impact:** ~Nk estimated wasted tokens
**Pattern:** <what happened>
**Recommendation:** Add to <location>:
```<config/code>```
**Apply this fix?**
Use AskUserQuestion to offer choices for each finding:
When applying:
.claude/hookify.<name>.local.md file.claude/skills/<name>/SKILL.md file stubnpx claudepluginhub ericboehs/claude-plugins --plugin session-improverAnalyzes Claude Code session logs to extract tool usage stats, thinking blocks, error patterns, debug trajectories, and generate actionable productivity recommendations. Provides cc-session CLI for overviews, timelines, searches.
Analyzes Claude Code sessions using MCP classifiers to detect usage patterns like correction spirals, rates severity, and provides concrete workflow improvements with metrics and advice.
Analyzes session friction with Claude Code skills, agents, permissions, hooks; gathers config from settings.json, CLAUDE.md; proposes targeted improvements.