skills.rest
lihaizhong
lihaizhongCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Finalize and archive completed changes in an experimental workflow.

Updated Feb 25, 2026
Search Tags:#CLI tool#workflow management#spec sync#change archiving#bugfix management
One-click install
npx skills add https://github.com/lihaizhong/communism --skill openspec-archive-change-lihaizhong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/lihaizhong/communism/tree/main/openspec-opc/.template/agent-config/skills/openspec-archive-change
Command: npx skills add https://github.com/lihaizhong/communism --skill openspec-archive-change-lihaizhong

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users finalize and archive completed changes in the experimental workflow, ensuring that the change is properly archived and documented.

Core Features & Use Cases

  • Finalize Changes: Archiving completed changes after they have been implemented.
  • Change Selection: Optionally specify a change name or select from available changes.
  • Status Checking: Verifying the completion status of artifacts and tasks.
  • Spec Sync Assessment: Assessing the delta spec sync state and managing spec impacts from bugfixes.

Quick Start

Archive the current change by running the command: `use openspec-archive-change archive --change "<change-name>"

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 changes in an experimental workflow?▼

To archive completed changes in an experimental workflow, you can use a CLI tool to finalize the process, ensuring artifacts and tasks are verified and properly documented before archiving.

What is spec sync state assessment in change archiving?▼

Spec sync state assessment in change archiving is the process of evaluating delta spec synchronization and managing spec impacts resulting from bugfixes during workflow finalization.

Do I need the openspec CLI to finalize and archive changes?▼

Yes, finalizing and archiving changes requires the openspec CLI and delta spec sync capabilities to verify artifact completion and manage spec synchronization states.

Can I select a specific change name when archiving workflow changes?▼

Yes, you can optionally specify a change name to archive or select from available changes, allowing targeted finalization of specific completed workflow tasks.

What's the best way to verify artifact and task completion before archiving?▼

The best way to verify artifact and task completion before archiving is using a CLI tool that checks status, assesses delta spec sync state, and manages spec impacts from bugfixes.

Why does change archiving require spec sync management for bugfixes?▼

Change archiving requires spec sync management for bugfixes because finalizing changes necessitates assessing delta spec sync state to ensure all spec impacts are properly documented and synchronized.

Related Skills

Explore More Software Engineering Skills→
ValorVieValorVie
5

openspec-archive-change

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

Community
Advanced
mufengbufengmufengbufeng
1

openspec-archive-change

Archive completed changes to date-prefixed paths with openspec CLI.

Community
Advanced
emergent-companyemergent-company
1

openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

Official
Advanced
unipds-engenharia-de-ia-aplicadaunipds-engenharia-de-ia-aplicada
1.0k

openspec-archive-change

Archive completed OpenSpec changes with artifact and task validation.

Official
Advanced