openspec-bulk-archive-change

Automates batch archiving of validated OpenScripture changes using CLI and delta specs.

Updated Jan 10, 2026

Search Tags:#automation #codebase #conflict-resolution #openspec #changes #batch-archive

Ready to run

npx skills add https://github.com/rick2047/WrestleGM --skill openspec-bulk-archive-change-rick2047

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive and manage multiple completed OpenSpec changes efficiently, reducing manual work and potential errors from handling each change individually.

Core Features & Use Cases

Bulk archiving: Move several closed changes into an archive with a single operation while preserving task and artifact state.
Conflict-aware syncing: Analyze delta specs and the codebase to resolve conflicts before archiving.
Validation & safety: Check artifact status and task completion prior to archive to prevent data loss.

Quick Start

Select active changes and follow the prompts to batch-archive them.

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 without losing task or artifact state?▼

To batch archive OpenSpec changes, you can automate the process by validating artifact status and task completion, then moving closed changes to a date-stamped archive path while preserving their state.

What is the best way to resolve delta spec conflicts when archiving multiple OpenSpec changes?▼

Resolving delta spec conflicts during archiving involves analyzing the codebase evidence to safely sync and move changes to the archive, preventing data loss from conflicting parallel modifications.

Can I archive multiple OpenSpec changes in parallel if they have conflicting delta specs?▼

Yes, you can archive parallel changes with conflicting delta specs because the process analyzes codebase evidence to resolve conflicts before moving changes to the archive directory.

Do I need the OpenSpec CLI to automate bulk archiving of codebase changes?▼

Yes, the OpenSpec CLI is required for operation to validate artifacts and tasks, apply date-stamped paths, and move changes to the openspec/changes/archive directory.

Why does batch archiving OpenSpec changes require validating artifact status first?▼

Validating artifact status and task completion prior to archiving is required to prevent data loss and ensure only properly closed changes are moved into the archive.