openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: Charles5277

Archive multiple completed openspec changes and resolve delta-spec conflicts.

45|3|Updated Jan 20, 2026

Search Tags:#archive #conflict-resolution #openspec #change-management #delta-specs #bulk-archive #codebase-search

Ready to run

npx skills add https://github.com/Charles5277/nuxt-supabase-starter --skill openspec-bulk-archive-change-charles5277

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/Charles5277/nuxt-supabase-starter/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/Charles5277/nuxt-supabase-starter --skill openspec-bulk-archive-change-charles5277

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed openspec changes in bulk, with conflict-aware archiving.

Core Features & Use Cases

Batch selection of multiple active changes for archiving
Conflict detection and resolution by inspecting delta specs and codebase
Safe archival: moves changes to openspec/changes/archive/YYYY-MM-DD-<name> with optional spec synchronization

Quick Start

Initiate a bulk archive to select active changes, resolve conflicts, and move archived changes into dated archive folders.

Frequently Asked Questions about openspec-bulk-archive-change

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

FAQPage Schema

How do I archive multiple openspec changes at once?▼

Batch archiving multiple openspec changes involves selecting active changes and moving them into dated archive folders. The process reads openspec CLI outputs, parses statuses, and moves change directories into openspec/changes/archive with a YYYY-MM-DD-<name> prefix.

How does delta-spec conflict resolution work when archiving parallel changes?▼

Delta-spec conflict resolution for parallel changes works by inspecting the delta specs and codebase to detect conflicts before archiving. This ensures artifacts and specs are synchronized and archived safely without overwriting conflicting modifications from concurrent changes.

When do I need to synchronize specs during a bulk archive?▼

You need to synchronize specs during a bulk archive when moving completed parallel changes that may have overlapping modifications. The conflict detection process inspects delta specs and the codebase to ensure artifacts and specs are synchronized before safely moving directories.

Can I archive openspec changes without resolving delta-spec conflicts?▼

Archiving openspec changes without resolving delta-spec conflicts is not recommended for parallel changes. The bulk archive process specifically applies conflict detection by inspecting delta specs and the codebase to ensure artifacts and specs are synchronized before moving directories to the archive.

What is the folder structure for archived openspec changes?▼

The folder structure for archived openspec changes uses openspec/changes/archive/YYYY-MM-DD-<name> format. Completed change directories are moved into this dated archive folder structure to maintain chronological organization and ensure artifacts and specs are safely preserved.