memory-log

Name: memory-log
Availability: InStock
Author: ishandhanani

Log milestones, findings, or results to ~/memory/ for future session context.

3|2|Updated Sep 3, 2025

Search Tags:#insights #memory #milestones #notes #session #log #project-memory

Ready to run

npx skills add https://github.com/ishandhanani/dotfiles --skill memory-log

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory-log
Source: https://github.com/ishandhanani/dotfiles/tree/main/agents/skills/memory-log
Command: npx skills add https://github.com/ishandhanani/dotfiles --skill memory-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Log milestones, findings, or results to ~/memory/ to preserve context across sessions.

Core Features & Use Cases

Record milestones, design decisions, bug root causes, or notable insights to a project-scoped memory folder.
Proactively capture outputs during active sessions or when triggered by notable events.
Organize entries under ~/memory/<project>/ so future prompts have context.
Retrieve and reference past entries to inform current work.

Quick Start

Invoke /memory-log to save a milestone or finding to ~/memory/<project>.

Frequently Asked Questions about memory-log

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

FAQPage Schema

How do I log project milestones and decisions to preserve context across sessions?▼

Log milestones, findings, or results to the memory store at ~/memory/ to preserve context across sessions. Applicable during design reviews, debugging, or research sessions where capturing decisions and outcomes improves collaboration and traceability.

What is project memory logging and when do I need it for debugging or research?▼

Project memory logging is recording milestones, bug root causes, and insights to a project-scoped memory folder. You need it during design reviews, debugging, or research sessions where capturing decisions and outcomes improves collaboration and traceability.

How do I save design review outcomes and bug root causes to a project memory store?▼

Save design review outcomes and bug root causes by invoking the memory-log command. The structured workflow classifies and writes entries under ~/memory/<project>/ so future prompts can reference past outputs.

Do I need a SKILL.md frontmatter to record session insights and milestones?▼

Yes, a SKILL.md frontmatter with name and description is required to record session insights and milestones. This frontmatter is required alongside a user-invocable command to trigger the structured workflow for writing and retrieving memory entries.

How are memory entries organized when logging findings to ~/memory/?▼

Memory entries are organized under ~/memory/<project>/ when logging findings. This project-scoped structure ensures future prompts and sessions have the necessary context to retrieve and reference past milestones and decisions.