openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict-aware syncing and metadata preservation.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/AdJIa/markdown-x --skill openspec-bulk-archive-change-adjia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/AdJIa/markdown-x/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/AdJIa/markdown-x --skill openspec-bulk-archive-change-adjia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation to reduce manual effort and preserve history across OpenSpec projects.

Core Features & Use Cases

  • Batch-archive selected changes with conflict-aware syncing
  • Detect and resolve overlapping delta specs by inspecting the codebase
  • Create dated archive directories while preserving metadata and history

Quick Start

Select the changes to archive, then confirm to complete the bulk archiving operation.

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 batch-archive completed OpenSpec changes to reduce manual effort?

Batch-archive completed changes by selecting multiple changes and confirming the operation. This processes them in parallel, checks the codebase for spec conflicts, and preserves metadata to reduce manual effort.

How does conflict-aware syncing work when archiving multiple changes?

Conflict-aware syncing inspects the codebase to detect and resolve overlapping delta specs before archiving. This prevents conflicts by ensuring changes are synchronized with the current codebase state during the batch process.

Do I need the OpenSpec CLI to run a bulk archive process?

Yes, the OpenSpec CLI is required to run the batch process for bulk archiving. It handles parallel processing, conflict detection, and metadata preservation within your codebase.

What is the best way to preserve metadata when archiving OpenSpec changes?

The best way to preserve metadata is using a bulk-archive operation that creates dated archive directories. This ensures history and metadata are maintained safely while resolving overlapping delta specs.

Why does bulk archiving fail when there are overlapping delta specs in the codebase?

Bulk archiving fails when overlapping delta specs cause conflicts in the codebase. The feature inspects the codebase to detect these conflicts, requiring resolution before the batch process can safely archive the changes.