10x-archive

Archives completed change folders into context/archive with git history preservation and roadmap closure.

Updated May 23, 2026
One-click install
npx skills add https://github.com/BMS-kmusial/bms-stream-monitor --skill 10x-archive-bms-kmusial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-archive
Source: https://github.com/BMS-kmusial/bms-stream-monitor/tree/main/.claude/skills/10x-archive
Command: npx skills add https://github.com/BMS-kmusial/bms-stream-monitor --skill 10x-archive-bms-kmusial

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 roadmap items and change metadata out of sync. ## Core Features & Use Cases - Safe archival with git mv: Moves a change folder from context/changes/ to context/archive/<created-date>-<change-id>/ using git mv so file history follows, and stamps change.md with status: archived and archived_at timestamps. - Lenient warn-only gate: Hard-blocks only on uncommitted changes or pre-existing staged files, while surfacing soft warnings for pending Progress items, missing impl-reviews, or missing SHA suffixes with a confirmation prompt. - Roadmap closure: Automatically flips the matching roadmap item's Status to done and appends an entry to the roadmap's Done section when a Change ID match exists. - Use Case: After finishing and reviewing an implementation change, run the archive command to move the folder, commit the rename, and close the corresponding roadmap item in one atomic commit. ## Quick Start Ask the assistant to archive the completed change by running /10x-archive followed by the change-id, for example /10x-archive oauth-login.

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 in git?

Run /10x-archive with the change-id or folder path. The skill moves context/changes/<change-id>/ to context/archive/<created-date>-<change-id>/ using git mv, stamps change.md with status: archived, and commits the rename in one commit.

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 be bundled into the archive commit. All other issues like pending progress items are warn-only.

Does archiving work if the project is not a git repository?

Yes, archiving still works without git. The skill prints a warning, falls back to a plain mv instead of git mv, and skips the archive commit step, though file history preservation is lost.

Can I unarchive or modify a change after it is archived?

No, archived folders under context/archive/ are read-only by convention and 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.

Why does the archive command warn about missing SHA suffixes?

Progress rows normally end with a commit SHA appended by /10x-implement at phase end. Rows missing the SHA suffix trigger a soft warning as a completeness signal, but they never block archiving since empty-diff phases legitimately lack SHAs.