Summarize session conversations into decision-focused history files with a searchable index.
npx skills add https://github.com/psw7205/skills --skill session-history-psw7205
Please help me install this Agent Skill. Skill: session-history Source: https://github.com/psw7205/skills/tree/main/skills/session-history Command: npx skills add https://github.com/psw7205/skills --skill session-history-psw7205
~/history/{YYYY}/{MM}/{DD}/{project}/ with kebab-case slugs and maintains a ~/history/index.jsonl index for deduplication and continuity. - Trigger discipline: Only activates on explicit end-of-session signals combined with recordable content (code changes, design decisions, or user feedback), avoiding noise from read-only sessions. - Use Case: After a long debugging and refactoring session, say "세션 정리해줘" and get a concise markdown record capturing the original request, key decisions with rationale, feedback applied, and follow-up tasks. ## Quick Start Ask the AI to summarize and save this session's work as a history file when you are wrapping up.High-intent search queries and answers about installing and using this skill.
Trigger the skill with an end-of-session phrase like "wrap up" or "save session". It summarizes the conversation focusing on decisions and rationale, then writes a markdown file to ~/history organized by date and project name.
Files are saved to ~/history/{YYYY}/{MM}/{DD}/{project_name}/{HH-mm}-{slug}.md, where the project name comes from the resolved current directory. An index.jsonl file in ~/history tracks every saved entry for lookup and deduplication.
It skips sessions with only Q&A or read-only exploration, sessions still in progress without an end signal, and sessions already saved once. This prevents incomplete or duplicate records.
The skill checks the index for an existing slug on the same date and appends a numeric suffix like -2 to the filename, so the second save does not overwrite the first.
Yes. Sessions containing design decisions or architecture discussions qualify as recordable content even without any code edits, since the decision rationale is the primary value being preserved.
usebonderySummarize documented architectural decisions and rationale for Bondery-specific systems.
abrahamgreysonRestore saved working context and project metadata from previous sessions.
christophevgTranscribe conversations into structured transcripts with YAML frontmatter and synthesis sections.
dgkngkDocument solved problems with steps, failures, and lessons in a knowledge base.