Session Refiner

Extract essential decisions, bugs, tasks, and code references into a 2,000–5,000 token Markdown session summary.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/amite/personal-triage-agent --skill session-refiner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Session Refiner
Source: https://github.com/amite/personal-triage-agent/tree/main/.claude/skills/session-refiner
Command: npx skills add https://github.com/amite/personal-triage-agent --skill session-refiner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Long coding sessions consume tokens and clutter context. Session Refiner extracts essential decisions, tasks, and code references into a compact 2,000–5,000 token Markdown summary to bridge sessions without losing continuity.

Core Features & Use Cases

  • Compact summaries: 2,000–5,000 token markdown recap of active tasks, decisions, and code references.
  • Two usage modes: Ask Claude for automatic summaries or run a local extractor script.
  • Use Case: Transition from one major feature to the next with a clean restart.

Quick Start

Say: "Use Session Refiner to create a summary." Then download the summary, start a new chat, and paste the summary at the top.

Frequently Asked Questions about Session Refiner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce token usage in long coding sessions?

Session Refiner condenses extended development work into a 2,000–5,000 token Markdown summary capturing active tasks, technical decisions, resolved issues, and code references. Extract essential context at session milestones, then paste the summary into a fresh chat to resume without reloading prior conversation history.

What should I include in a session summary to maintain continuity?

Structure your summary with Active Tasks, Key Technical Decisions, Resolved Issues, Code References, and Key Findings. Session Refiner formats these sections as copy-paste-ready Markdown designed for immediate handoff between development phases or team members.

Can I automate session summaries or do I need to write them manually?

Session Refiner supports both modes: request automatic summaries directly in Claude chat, or run the included local extractor script for workflow integration. Both methods produce structured Markdown output compatible with script-based and manual workflows.

When should I create a session summary during development?

Create a summary at feature transitions, milestone completions, or when context grows beyond your token budget. Session Refiner bridges gaps between sessions without losing momentum, making it ideal for multi-day projects or when switching between major tasks.

Does Session Refiner work with existing markdown notes or code repositories?

Yes. Session Refiner extracts references to code files, decisions, and findings from your active session and formats them as Markdown suitable for import into documentation systems or version-control commit messages.