Archive Skill - A Tool for Archiving Session Experiences and Reusing Knowledge Across Sessions

Skill Overview

The Archive skill archives learning outcomes, debugging solutions, and deployment logs from sessions into the .archive/yyyy-mm-dd/ directory. It preserves project knowledge in indexed Markdown files with searchable tags for quick reference and reuse in future sessions.

Applicable Scenarios

1. Record important tasks after completion: After completing a deployment, migration, or major feature development, archive the key steps, configurations, and commands to avoid having to retrace everything next time.
2. Save solutions after resolving difficult bugs: Once complex debugging is complete, organize and archive the symptoms, root-cause analysis, and fix commands so that similar errors can be addressed directly in the future.
3. Check the archive before troubleshooting infrastructure issues: Before starting to debug deployment, CI, or environment problems, first search .archive/MEMORY.md to confirm whether similar issues have been resolved before.

Core Features

1. Structured archiving workflow: Create a .archive/YYYY-MM-DD/ directory by date, write Markdown files with YAML frontmatter (tags, category, related), and use descriptive filenames (such as cloudwatch-logging.md) for easy identification.
2. MEMORY.md index maintenance: Each time an archive entry is created, automatically append a summary line under the corresponding category in .archive/MEMORY.md, forming a browsable cross-session directory.
3. Categorization and search system: Supports five categories: infrastructure, release, debugging, feature, and design. Related archives are linked through the related field. Full-text searches can be performed with grep -ri "keyword" .archive/.

Frequently Asked Questions

Where is archived content stored, and will it be committed to Git?

Archives are stored locally in the project’s .archive/ directory, organized into subdirectories by date. This skill requires adding .archive/ to .gitignore, so archives are purely local notes and will not be committed to the repository.

How can I retrieve previously archived experience?

There are two ways: first, read the .archive/MEMORY.md index, locate the relevant entry by category, and then open the specific file; or directly run grep -ri "keyword" .archive/ to perform a full-text search across all archives.

When should an archive be created?

There are four occasions: after completing an important task (deployment, migration, or major feature); after resolving a difficult debugging issue; after completing a multi-step process with valuable lessons; or when you directly tell the agent, “archive this.” Before archiving, the system first checks MEMORY.md for existing related records to avoid duplication.