openspec-bulk-archive-change

Archive multiple OpenSpec changes with conflict detection and spec synchronization.

Updated Feb 4, 2026

Search Tags:#archive #conflict-resolution #openspec #changes #bulk-archive #spec-sync

Ready to run

npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-bulk-archive-change-sqdr2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/SQDR2/PortableConversationScriptAssistant/tree/main/.github/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-bulk-archive-change-sqdr2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation to streamline change management for OpenSpec projects.

Core Features & Use Cases

Batch-select active changes for archiving and preview outcomes with a consolidated status report.
Detect cross-change spec conflicts, automatically reason about implementations in the codebase, and resolve or order specs before archiving.
Preserve critical configuration and ensure archive directories follow the date-named convention (YYYY-MM-DD-<change>), while keeping .openspec.yaml intact.
Prompt for a single confirmation to proceed with the entire batch, and clearly report success, skips, or failures.

Quick Start

Select the changes when prompted, then confirm to perform the bulk archive.

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 the same time?▼

To bulk-archive multiple OpenSpec changes, batch-select active changes, preview the consolidated status report, and confirm the single prompt to execute the entire batch operation.

What happens if completed changes share conflicting specs before archiving?▼

When bulk archiving detects cross-change spec conflicts, it automatically reasons about codebase implementations to resolve or order specs before moving the changes to the archive directory.

Does the bulk archive process preserve .openspec.yaml configuration?▼

Yes, the bulk archive process preserves the .openspec.yaml configuration file and ensures archive directories follow the date-named convention (YYYY-MM-DD-<change>) for safe project housekeeping.

Can I preview the outcome before archiving a batch of changes?▼

Yes, you can preview outcomes with a consolidated status report that detects cross-change spec conflicts and clearly reports success, skips, or failures before you confirm the batch execution.

Why does spec synchronization run before moving changes to the archive?▼

Spec synchronization runs before archiving to ensure automated spec alignment, resolving any cross-change conflicts so the codebase and specs remain consistent when changes are moved.