archive_skill

Overview

This skill captures and indexes session learnings, debugging solutions, and deployment logs into a local .archive/yyyy-mm-dd/ folder as searchable Markdown with tags. It maintains a central .archive/MEMORY.md index for quick cross-session lookup and reuse. Use it to preserve reproducible fixes, deployment notes, and multi-step lessons that save time later.

How this skill works

The skill inspects recent session context and prompts the user to create a new archive entry when a significant task completes or the user says "archive this." It writes a Markdown file with YAML frontmatter (tags, category, optional related links) into a dated .archive directory and appends a one-line entry to .archive/MEMORY.md for fast discovery. Existing related archives are detected and linked in the frontmatter.

When to use it

• After completing a deployment, migration, or major feature delivery
• When you resolve a tricky bug or discover a reproducible fix
• At the end of a multi-step process with useful commands or gotchas
• Whenever you say "archive this" to preserve session context
• Before removing local debugging artifacts or rotating secrets

Best practices

• Keep entries concise and reproducible: include exact commands and outputs
• Use descriptive filenames (e.g., cloudwatch-logging.md) and clear categories
• Always update .archive/MEMORY.md immediately after creating a file
• Add related frontmatter links when similar archives exist to build context
• Keep .archive/ in .gitignore so notes remain local and private

Example use cases

• Record an ECS deploy troubleshooting session with commands and CloudWatch snippets
• Save a resolved CI failure with the patch, test commands, and root cause
• Archive release notes for TestFlight or versioning steps after a release
• Capture a complex feature design decision and implementation notes for later reference
• Log environment or secrets rotation steps that must be repeated for future deploys