openspec-bulk-archive-change

Batch-archive multiple OpenSpec changes into date-stamped directories with conflict resolution.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/kunish/muon --skill openspec-bulk-archive-change-kunish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/kunish/muon/tree/main/.github/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/kunish/muon --skill openspec-bulk-archive-change-kunish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes from an OpenSpec project in a single operation to simplify release management and reduce manual steps.

Core Features & Use Cases

  • Bulk-archive: Archive several changes in one batch, preserving history and moving them into a date-stamped archive path.
  • Conflict detection & resolution: Detect delta-spec conflicts across selections and guide or perform resolution by inspecting the codebase.
  • Audit-friendly reporting: Produce a consolidated status summary of archived, skipped, and failed changes, with a spec-sync trail.
  • Safe archive policy: Preserve critical configuration, avoid overwriting existing archives when possible, and warn on conflicts.

Quick Start

Initiate a batch archive by selecting multiple changes, confirm the operation, and review the resulting archive structure.

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?

To archive multiple OpenSpec changes, you initiate a batch operation that interactively selects completed changes, validates delta-spec conflicts, and moves them into a date-stamped archive path.

What happens when delta-specs conflict during a bulk archive?

When delta-spec conflicts occur during a bulk archive, the system detects them across selections and guides resolution by inspecting the codebase to ensure safe archival.

Can I preserve configuration files when archiving OpenSpec changes?

Yes, the safe archive policy preserves critical configuration files, avoids overwriting existing archives, and produces an audit-friendly status summary of archived, skipped, and failed changes.

How does batch archiving handle reporting for completed change management?

Batch archiving produces a consolidated, audit-friendly status summary tracking archived, skipped, and failed changes, alongside a spec-sync trail for release management.

Do I need an interactive prompt to select changes for OpenSpec archival?

Yes, the bulk archival process enforces interactive selection, requiring you to select and confirm multiple changes before executing the batch operation to prevent accidental data loss.