session-end

To archive a development session and save tokens, you can automate the process by generating summaries of code changes and commit history using Bash scripts and templates, which avoids extensive file reads and reduces LLM token consumption.

Generating session logs from git history is best handled by leveraging git commands and cached data to extract commit messages and task status, automatically archiving the output into categorized directories for a clean historical record.

Session management works with git integration for task tracking by utilizing git commands to pull commit history and code changes, ensuring that task progress and session state are accurately captured and archived.

To clean up session state after completing a feature, you can run an automated archival process that finalizes task tracking, generates a comprehensive summary of code changes, and manages file archival into categorized directories.

You can use Bash scripts to optimize token usage during code archival by analyzing changes and generating structured logs from cached data, bypassing the need for LLM-generated narratives and extensive file reads.