bye

Records session summaries and manages lifecycle of tasks and notes in Todoist via natural language commands.

2|Updated Feb 7, 2026

Search Tags:#auditing #version-control #session-history #restoration #wrap-up #sessionlog

Ready to run

npx skills add https://github.com/eins78/skills --skill bye

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bye
Source: https://github.com/eins78/skills/tree/main/skills/bye
Command: npx skills add https://github.com/eins78/skills --skill bye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restores the full session history to prevent context loss from automated compacting, enabling accurate wrap-up, commit logging, and next-step planning.

Core Features & Use Cases

Full-history restoration: recovers prior messages, decisions, and actions from Claude Code and Cursor storage.
Sessionlog creation and updates: generates or updates sessionlogs with an auditable trail of activity.
Git and project-status integration: creates commits for changes and traces repository state for post-session review.
Parallel-session safeguards: filters out work from unrelated sessions and logs restoration attempts for auditability.

Quick Start

Invoke /bye at session end to restore history, generate a sessionlog, commit changes, and summarize next steps.

Frequently Asked Questions about bye

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

FAQPage Schema

How do I restore full session history in Claude Code after automated context compaction?▼

Session history restoration recovers prior messages, decisions, and actions from Claude Code and Cursor storage to prevent context loss from automated compacting. It requires restoration tooling and references specific restoration guides to ensure safe, auditable results.

What is the best way to wrap up a coding session and create an auditable sessionlog?▼

Session wrap-up creates or updates sessionlogs with an auditable trail of activity, commits changes via Git integration, and summarizes next steps. It handles normal, plan-execution, and plan-creation sessions by restoring full history first to ensure accurate context.

How do I generate a git commit and next-step summary when finishing a development session?▼

Git and project-status integration creates commits for changes made during the session and traces repository state for post-session review. It operates after full-history restoration, ensuring the commit log accurately reflects all prior actions and decisions.

Does session history restoration work with parallel coding sessions without mixing up context?▼

Parallel-session safeguards filter out work from unrelated sessions and log restoration attempts for auditability. This ensures the restored history and generated sessionlog only capture activity relevant to the current session being wrapped up.

When do I need to restore session history before wrapping up a coding project?▼

Restoration is needed when automated compacting has truncated the context window, hindering accurate wrap-up, commit logging, and next-step planning. If context loss has occurred, invoking a wrap-up tool restores the full history before generating final sessionlogs.

Why does my session wrap-up lack complete context and miss earlier decisions and actions?▼

Incomplete context during wrap-up is caused by automated compacting truncating session history. Restoring the full session history before wrapping up prevents this context loss, enabling accurate sessionlog creation and next-step summarization.