skills.rest
yazelin
yazelinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed openspec changes with date-stamped directories.

31|10|Updated Dec 10, 2025
Search Tags:#workflow#archive#CLI tool#change management#data archiving
One-click install
npx skills add https://github.com/yazelin/ching-tech-os --skill openspec-archive-change-yazelin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/yazelin/ching-tech-os/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/yazelin/ching-tech-os --skill openspec-archive-change-yazelin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed changes in the experimental workflow, ensuring that changes are securely stored and organized after implementation.

Core Features & Use Cases

  • Archive Completed Changes: Securely archive changes once they are implemented and complete.
  • Change Selection: Optionally specify a change name or select from available changes.
  • Status Verification: Checks for artifact and task completion before archiving.
  • Spec Sync Assessment: Evaluates delta spec sync state and prompts for sync if necessary.
  • Archive Execution: Moves the change directory to the archive location with a date-stamped name.

Quick Start

Use the openspec-archive-change skill to archive the change named 'update-123'.

Frequently Asked Questions about openspec-archive-change

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

FAQPage Schema
How do I archive completed workflow changes with a date-stamped directory?▼

You can archive completed workflow changes by using a CLI tool to verify artifact and task completion, then moving the change directory to an archive location with a date-stamped name.

What is the process for verifying task and artifact completion before archiving a change?▼

Change archiving requires verifying artifact and task completion to ensure all implementation steps are finished before securely storing the change directory in the archive.

Does the openspec CLI tool support selecting specific changes to archive from a list?▼

Yes, the openspec CLI supports archiving user-specified change names or selecting available changes from a list to finalize and store completed workflow modifications.

How do I assess spec sync state before archiving data changes?▼

The archiving process evaluates delta spec sync state and prompts for synchronization if necessary, ensuring all specifications are aligned before the change is archived.

Do I need the openspec CLI installed to automate change management and archiving?▼

Yes, the openspec CLI is a required dependency for automating change management tasks, including verifying status and executing the final archive of completed changes.

What happens if spec sync state is not aligned before archiving a change?▼

If spec sync state is not aligned, the archive process assesses the delta and prompts for synchronization to ensure data consistency before moving the change directory.

Related Skills

Explore More Software Engineering Skills→
DanielShuguangDanielShuguang

openspec-onboard

Guides users through the complete OpenSpec workflow cycle on their own codebase.

Community
Intermediate
cookeyholdercookeyholder

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict resolution and date-stamped directories.

Community
Advanced
jason23452jason23452

openspec-archive-change

Archive completed changes while preserving .openspec.yaml configuration.

Community
Advanced
ValorVieValorVie
5

openspec-archive-change

Archive a completed change with artifact checks and delta-spec sync.

Community
Advanced