openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: Atman

Batch-archive completed OpenSpec changes while resolving delta-spec conflicts.

Updated Aug 23, 2026

Search Tags:#codebase #conflict-resolution #openspec #changes #delta-specs #bulk-archive

Ready to run

npx skills add https://github.com/atman-33/skills --skill openspec-bulk-archive-change-atman-33

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in OpenSpec in a single operation to reduce manual work and keep the change history clean.

Core Features & Use Cases

Batch archive: archive several completed changes in one action.
Conflict-aware: detects delta-spec conflicts across selected changes and resolves them using evidence from the codebase.
Safe archival: preserves the OpenSpec configuration and uses date-stamped archive paths to maintain traceability.

Quick Start

Use the openspec-bulk-archive-change skill to batch archive all active changes after verifying they are completed and ready for archival.

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?▼

Batch archiving multiple OpenSpec changes requires the OpenSpec CLI to process completed changes in a single pass, prompting for selection and reporting outcomes for each change individually.

How does bulk archiving handle delta-spec conflicts across changes?▼

When batch archiving, the process detects delta-spec conflicts across selected changes and resolves them using codebase evidence, ensuring the final archived state accurately reflects the actual codebase.

Do I need the OpenSpec CLI to batch archive changes?▼

Yes, the OpenSpec CLI is required to run the bulk archive operation. It facilitates prompting for change selection, resolving delta-spec conflicts, and moving completed changes to date-based archive paths.

What is the best way to keep OpenSpec change history clean after completing multiple changes?▼

The best way to keep change history clean is to batch archive completed changes in a single operation. This preserves the .openspec.yaml configuration and uses date-based archive paths to maintain traceability.

Does archiving changes preserve the OpenSpec configuration file?▼

Yes, the bulk archive operation preserves the .openspec.yaml configuration file when archiving changes. It utilizes date-based archive paths to maintain historical traceability and reports outcomes for each change.

Why should I use batch archiving instead of archiving changes one by one?▼

Batch archiving reduces manual work by processing multiple completed changes simultaneously, automatically detecting and resolving cross-change delta-spec conflicts using codebase evidence instead of handling each change individually.