openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: open-platform-model

Batch archive multiple completed OpenSpec changes with conflict detection and status validation.

Updated Dec 8, 2025

Search Tags:#conflict-resolution #openspec #workflow-automation #change-management #codebase-analysis #bulk-archive

Ready to run

npx skills add https://github.com/open-platform-model/cli --skill openspec-bulk-archive-change-open-platform-model

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/open-platform-model/cli/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/open-platform-model/cli --skill openspec-bulk-archive-change-open-platform-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in OpenSpec by batch archiving, reducing manual toil and improving traceability.

Core Features & Use Cases

Batch-archive: archive multiple changes in a single operation
Conflict detection and automated resolution by analyzing delta specs and the codebase
Preserve metadata and maintain integrity with safeguards for incomplete or conflicting changes
Use Case: maintenance of parallel changes across releases with minimal disruption

Quick Start

Run the bulk archive command to process all ready changes.

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 multiple completed OpenSpec changes in one operation?▼

Batch-archiving multiple OpenSpec changes requires processing all ready changes in a single bulk operation. This reduces manual toil by validating statuses and detecting conflicts across parallel workflows, archiving them safely while preserving history for recovery.

How does conflict detection work when archiving parallel changes in OpenSpec?▼

Conflict detection during archiving analyzes delta specs and the codebase to identify overlapping modifications. It validates statuses and flags incomplete or conflicting changes, offering optional automated resolution to ensure metadata integrity is preserved safely across parallel workflows.

Do I need the openspec CLI to perform bulk archiving of changes?▼

Yes, the openspec CLI is required to perform bulk archiving. You also need existing change data stored under the openspec/changes directory, as the operation relies on this structure to validate statuses, detect conflicts, and preserve history for recovery.

What is the best way to maintain parallel changes across releases with minimal disruption?▼

The best way to maintain parallel changes across releases is using batch archiving. This approach processes multiple completed changes simultaneously, applying conflict detection and optional resolution to minimize disruption and improve traceability across workflows.

Can incomplete or conflicting OpenSpec changes be archived safely?▼

Incomplete or conflicting changes are safeguarded during archiving. The process validates statuses and detects conflicts before proceeding, preserving metadata and maintaining integrity by offering optional resolution rather than blindly archiving problematic data.

Why does batch archiving preserve history for OpenSpec change recovery?▼

Batch archiving preserves history to ensure recovery capabilities. By maintaining metadata integrity and safeguarding against incomplete or conflicting changes during the bulk operation, the system keeps a reliable traceable record of completed modifications for future reference.