archive

Move completed morkit changes to the archive subfolder and update metadata.

3|Updated Apr 20, 2026

Search Tags:#automation #workflow #metadata #archive #change-management #morkit

Ready to run

npx skills add https://github.com/mor-duongmh/morkit-plugin --skill archive-mor-duongmh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/mor-duongmh/morkit-plugin/tree/main/plugins/morkit/skills/archive
Command: npx skills add https://github.com/mor-duongmh/morkit-plugin --skill archive-mor-duongmh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed morkit changes by moving them from the active spec directory to the archive folder and marking them as archived in metadata, reducing clutter and improving traceability.

Core Features & Use Cases

Move completed changes from the active workspace into an archive structure.
Update metadata to reflect archived status and timestamp.
Provide safeguards and prompts to prevent archiving in-progress work.

Quick Start

Run the archive command to retire a completed change.

Frequently Asked Questions about archive

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

FAQPage Schema

How do I archive a completed change in my workflow without losing traceability?▼

To archive a completed change, you move it from the active spec directory to an archive subfolder and update its metadata. This marks the change as archived with a timestamp, reducing workspace clutter while preserving historical traceability.

What happens if I try to archive a change with incomplete tasks?▼

Archiving a change with incomplete tasks triggers a confirmation guardrail. The system validates task completion before moving files and will prompt you to confirm if you attempt to archive work that is still in progress.

Can I prevent overwriting an existing archive when moving completed changes?▼

Yes, the archive process includes a guardrail to prevent overwriting existing archives. When moving a completed change to the archive subfolder, it ensures no previous archive data is lost.

How do I update metadata to mark a workflow change as archived?▼

You update metadata to mark a workflow change as archived by modifying the .meta.json file. The process automatically updates the archived status and timestamp during the move operation.

Does archiving a change require a specific change-name input?▼

Archiving a change supports optional change-name input. You can run the command to retire a completed change by providing a specific name, or it will process the active change based on the current context.

What is the best way to safely retire completed changes from an active workspace?▼

The best way to retire completed changes is to move them from the active spec directory to an archive subfolder. This process validates task completion, updates metadata, and prevents overwriting existing archives.