diary

Log session accomplishments, decisions, and structured handoffs to SQLite.

412|45|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/cwinvestments/memstack --skill diary-cwinvestments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diary
Source: https://github.com/cwinvestments/memstack/tree/main/skills/diary
Command: npx skills add https://github.com/cwinvestments/memstack --skill diary-cwinvestments

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that all accomplished work, decisions made, and next steps are meticulously logged, creating a searchable history and a clear handover for future sessions.

Core Features & Use Cases

  • Session Summarization: Automatically captures key details like project name, date, duration, accomplishments, files changed, and commits.
  • Decision Logging: Extracts and saves critical decisions made during the session for future reference and cross-project insights.
  • Structured Handoff: Provides clear instructions for resuming work, including in-progress tasks and uncommitted changes.
  • Use Case: At the end of a coding session, you can simply say "save diary" to generate a comprehensive log that includes what you built, any problems you hit, and exactly where to pick up next time.

Quick Start

Use the diary skill to log the current session's accomplishments and decisions.

Frequently Asked Questions about diary

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

FAQPage Schema
How do I log session progress and decisions for code handoff?

To log session progress and decisions, this Skill captures project context, date, duration, files modified, and git commits to create a structured handoff. It automatically generates a comprehensive summary for future development sessions.

What is the best way to document code history and developer productivity insights?

Documenting code history and developer productivity is achieved by extracting critical decisions as searchable insights. The system stores these records in a persistent SQLite database and saves markdown backups for future reference.

How do I create a structured handoff for uncommitted changes and in-progress tasks?

Creating a structured handoff for uncommitted changes involves logging your current session's accomplishments and next steps. The Skill provides clear instructions for resuming work, including in-progress tasks and uncommitted changes.

Do I need sqlite3 to save session accomplishments and markdown backups?

Yes, sqlite3 is required to save session accomplishments because the Skill relies on SQLite database interaction for persistent storage. It also generates markdown backups of your session logs.

Can I use this session management tool for cross-project decision tracking?

Yes, you can use this session management tool for cross-project decision tracking. It extracts decisions made during your coding sessions and saves them as searchable insights for cross-project reference.

Why does logging session context require a database instead of just markdown files?

Logging session context requires a database to provide persistent storage and enable searchable queries across your project history. Markdown backups are also generated alongside the database records for accessible file-based documentation.