10x-archive

Archive completed change folders into context/archive with git mv and frontmatter stamping.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/michaail/hybrid-logs-analyzer --skill 10x-archive-michaail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-archive
Source: https://github.com/michaail/hybrid-logs-analyzer/tree/main/.cursor/skills/10x-archive
Command: npx skills add https://github.com/michaail/hybrid-logs-analyzer --skill 10x-archive-michaail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed change folders accumulate in context/changes/ and clutter the active workspace, while manually moving them loses git history and leaves change.md status and roadmap items inconsistent. ## Core Features & Use Cases - History-preserving move: Moves context/changes/<change-id>/ to context/archive/<created-date>-<change-id>/ using git mv so file history follows, with a plain mv fallback outside git repos. - Status stamping and roadmap closure: Stamps change.md with status: archived, archived_at, and updated, then flips the matching roadmap item's Status to done and appends a ## Done entry. - Lenient warn-only gate: Hard-blocks only on uncommitted changes or pre-existing staged files; incomplete Progress, missing impl-review, and missing SHA suffixes surface as warnings with a confirmation prompt. - Use Case: After finishing and reviewing a feature change, run the archive command to relocate the folder, close its roadmap item, and commit everything as a single chore(archive) commit. ## Quick Start Archive the completed change oauth-login by running /10x-archive oauth-login and confirming any warnings shown.

Frequently Asked Questions about 10x-archive

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

FAQPage Schema
How do I archive a completed change folder?

Run /10x-archive with the change-id, for example /10x-archive oauth-login or /10x-archive @context/changes/oauth-login/. The skill moves the folder to context/archive/<created-date>-<change-id>/, stamps change.md, and commits the result.

What blocks the 10x-archive command from running?

Only two conditions hard-block archiving: uncommitted changes inside the change folder, and pre-existing staged changes elsewhere that would leak into the archive commit. All other issues like incomplete Progress items or missing impl-review are warn-only.

Does archiving work without git?

Yes. If git is unavailable or the directory is not a git repository, the skill prints a warning, falls back to a plain mv instead of git mv, and skips the archive commit. File history preservation is lost in that case.

Does archiving update the project roadmap automatically?

Yes. If context/foundation/roadmap.md contains an item whose Change ID exactly matches the archived change, the skill sets its Status to done, appends a ## Done entry, and bumps the updated date. No match leaves the roadmap untouched.

Can I unarchive or edit an archived change folder?

No. Archived folders under context/archive/ are read-only by convention, and all other 10x skills refuse to write into them. To revisit the work, open a new change with /10x-new and reference the archived folder for context.