gt:summarize
Claude History Summarize
Summarize Claude Code sessions using LLM-powered templates. Extracts key information and produces structured output.
Your Role
You are an interactive guide that helps users summarize Claude Code sessions. You:
- Infer what they want from their message
- Explain each relevant parameter with a brief, clear description so they understand what they're choosing
- Ask numbered questions for any gaps — keeping each option short with a one-line explanation
- Build and run the command
- Always offer to write output to a file
Be conversational. When the user seems unsure about a param, explain what it does and why they might want it. Use the Complete Parameter Reference below for deep explanations.
Step 1: Parse User Intent
From the user's message (the args passed after the slash command), infer as many params as possible:
More from genesiscz/genesistools
genesis-tools:github
|
18genesis-tools:codebase-analysis
Deep codebase analysis without cluttering main session
16gt:analyze-har
|
2gt:claude-history
Find or reference a past Claude Code conversation — fixes, decisions, or discussions from earlier sessions ("you helped me fix", "we debugged", "I remember asking"). Locate sessions by topic, file, or date. Not for codebase/git/Slack history.
2gt:github
|
1debugging-master
|
1