Overview

Archive captures session learnings, debugging solutions, and deployment logs into dated markdown files under .archive/, with searchable tags. It creates an indexed, reusable knowledge base and maintains a MEMORY.md index for cross-session reuse.

How This Skill Works

When triggered, the skill checks MEMORY.md for related archives, creates a .archive/YYYY-MM-DD/ directory if needed, writes a markdown file with YAML frontmatter (tags, category, and optional related), and updates MEMORY.md with a one-line entry. Descriptive filenames are encouraged, and .archive/ should be ignored by Git to keep notes local.

When to Use It

• After completing a significant task (deploy, migration, major feature)
• After resolving a tricky debugging session
• When the user says archive this
• After any multi-step process with learnings worth preserving
• Before repeating a process in a new session to reuse prior learnings

Quick Start

1. Step 1: Read .archive/MEMORY.md to identify related entries
2. Step 2: Create .archive/YYYY-MM-DD/ and a descriptive markdown file (e.g., cloudwatch-logging.md)
3. Step 3: Write YAML frontmatter with tags, category, and optional related; update MEMORY.md

Best Practices

• Keep entries concise but reproducible
• Use descriptive filenames (e.g., cloudwatch-logging.md)
• Include YAML frontmatter with tags, category, and optional related
• Always update MEMORY.md after creating an archive
• .archive/ must be in .gitignore; notes are local-only

Example Use Cases

• Archive a deployment run with steps, fixes, and rollback commands
• Archive a flaky API debugging session with commands to reproduce
• Archive a feature rollout plan including changelog references
• Archive a database migration script and rollback instructions
• Archive a CI/CD pipeline optimization session with config changes

Frequently Asked Questions