10x-archive

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

Updated May 24, 2026
One-click install
npx skills add https://github.com/DevMachaj/Projekt-certyfikacyjny --skill 10x-archive-devmachaj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-archive
Source: https://github.com/DevMachaj/Projekt-certyfikacyjny/tree/main/.claude/skills/10x-archive
Command: npx skills add https://github.com/DevMachaj/Projekt-certyfikacyjny --skill 10x-archive-devmachaj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed change folders accumulate in context/changes/ with no consistent way to close them out, leaving stale work mixed with active changes and roadmap items that never get marked done. ## Core Features & Use Cases - Safe archival with git history: Moves a change folder from context/changes/ to context/archive/<created-date>-<change-id>/ using git mv, stamps change.md with archived status and timestamp, and commits the result. - Lenient warn-only gate: Hard-blocks only on uncommitted changes or pre-existing staged files; incomplete progress, missing impl-reviews, and unexpected statuses surface as warnings 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 a feature change, run the archive command to move the folder, stamp its metadata, close the roadmap item, and produce a single clean archive commit. ## Quick Start Ask the assistant to archive a 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?

Run /10x-archive followed by the change-id or path, such as /10x-archive oauth-login. The skill moves the folder to context/archive/<created-date>-<change-id>/, stamps change.md with archived status, and commits the result.

What blocks the archive command from running?

Only two conditions hard-block: 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 or missing reviews are warnings you can override.

Does archiving a change update the 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 section entry, and stages the edit into the archive commit when the file was previously clean.

Can I archive a change without git installed?

Yes. The skill warns that it is not a git repository, falls back to a plain mv instead of git mv, and skips the commit step. You lose history preservation but the folder move and frontmatter stamping still work.

Can I unarchive or modify an archived change?

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.