10x-archive

Automates moving completed change folders to archive directory and updating status.

Updated May 18, 2026
One-click install
npx skills add https://github.com/PixelSculptor/osce-triager --skill 10x-archive-pixelsculptor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-archive
Source: https://github.com/PixelSculptor/osce-triager/tree/main/.claude/skills/10x-archive
Command: npx skills add https://github.com/PixelSculptor/osce-triager --skill 10x-archive-pixelsculptor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the archiving process for completed changes, ensuring project integrity and providing a clear history of change management.

Core Features & Use Cases

  • Change Archiving: Automatically moves completed change folders to an archive directory and updates status.
  • Integration with Project Structure: Works within the project's context/changes/ and context/archive/ directories.
  • Error Handling: Provides detailed error messages and options for resolving issues like uncommitted changes or missing information.

Quick Start

To archive a completed change, use the command: /10x-archive <change-id>.

Frequently Asked Questions about 10x-archive

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

FAQPage Schema
How do I archive completed changes in a git repository to maintain project integrity?

To archive completed changes, this Skill automatically moves the relevant change folder from your active context directory to an archive directory and updates its status. It handles errors like uncommitted changes to ensure project integrity throughout the archiving process.

What is the best way to automate moving completed project changes to an archive directory?

Automating change archiving is best handled by this Skill, which moves completed change folders to the archive directory and updates their status. It integrates directly with your project structure and version control system to maintain project integrity.

How does change archiving handle uncommitted changes or missing information in version control?

Change archiving handles uncommitted changes and missing information by providing detailed error messages and options for resolving issues. This ensures your version control system remains consistent before moving the folder to the archive directory.

Do I need a specific project context directory structure to use automated change archiving?

Yes, automated change archiving requires access to your project's context directory and version control system. It specifically works within the project's `context/changes/` and `context/archive/` directories to move completed folders and update status.

Why does my project change archiving process fail when I have uncommitted git changes?

Your change archiving process fails because uncommitted git changes threaten project integrity. This Skill detects uncommitted changes and missing information, providing detailed error messages and options to resolve the issues before moving the folder to the archive directory.