openspec-bulk-archive-change

Archive multiple completed changes in a batch with explicit user confirmation.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-bulk-archive-change-mazhewitt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/mazhewitt/budget-analyser/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-bulk-archive-change-mazhewitt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation to streamline maintenance of multiple parallel changes.

Core Features & Use Cases

  • Batch processing of multiple changes in one go with auditable results
  • Conflict-aware resolution to avoid overwriting work
  • Safe, guided user prompts that require explicit confirmation before archiving

Quick Start

Archive the active changes by selecting them, confirming the batch, and letting the tool perform the archive while preserving history.

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 changes in a repository with parallel branches?

Batch archiving completed changes consolidates multiple finished items into a single operation, streamlining project maintenance for parallel changes. A guided flow requires explicit user confirmation to safely process the batch while preserving history.

What is conflict-aware resolution when archiving multiple changes?

Conflict-aware resolution checks for overlapping modifications during batch archiving to avoid overwriting parallel work. This mechanism ensures that completed changes are validated before being archived together, preserving history safely.

Do I need the openspec CLI to perform a batch archive of changes?

Yes, the openspec CLI is required to perform this batch archiving flow. It provides the auditable, guided user prompts and explicit confirmation steps necessary to safely archive completed changes while preserving project history.

How does conflict resolution work when batch archiving parallel changes?

Conflict resolution during batch archiving prevents overwriting active work by validating parallel changes before processing. The guided flow requires explicit user confirmation, ensuring an auditable trail and safe history preservation for the repository.

Can I select specific completed changes to archive together instead of all active items?

Yes, the batch archive flow allows you to select specific completed changes from the active set. After selecting, you confirm the batch, and the tool performs the archiving operation while preserving history and generating auditable results.