openspec-bulk-archive-change

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

Batch-archive completed OpenSpec changes with conflict resolution and date-stamped directories.

Updated Apr 9, 2026

Search Tags:#automation #archive #conflict-resolution #openspec #version-control #batch-processing #change-management

Ready to run

npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill openspec-bulk-archive-change-cookeyholder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/cookeyholder/django-devcontainer-template/tree/main/.agent/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill openspec-bulk-archive-change-cookeyholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing OpenSpec changes can be time-consuming when many completed items accumulate. This skill enables batch-archiving to streamline cleanup and preserve historical context.

Core Features & Use Cases

Batch archive: archive multiple changes in a single operation to save time.
Conflict-aware: detects overlapping delta specs and resolves conflicts by inspecting code references.
Audit trail: preserves original change data and archives them with a date-stamped path for traceability.

Quick Start

Batch-archive all completed OpenSpec changes after validating their state.

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

You can batch-archive multiple OpenSpec changes by processing all completed items in a single operation, which streamlines cleanup and preserves historical context. The batch archive function detects overlapping delta specs and resolves conflicts by inspecting code references.

What happens when archived OpenSpec delta specs have conflicts?▼

When delta specs conflict during OpenSpec archival, the conflict-aware mechanism detects overlapping changes and resolves them by inspecting underlying code references. This ensures safe archival while preserving the original change data.

How does OpenSpec change management preserve an audit trail?▼

OpenSpec change management preserves an audit trail by retaining original change data and archiving completed items into date-stamped directories. This structured path ensures traceability and historical context for future reference.

Can I automate spec synchronization for completed OpenSpec changes?▼

Yes, you can automate spec synchronization by batch-archiving completed OpenSpec changes. This automated process validates the state of completed items before moving them, satisfying requirements for safe archival and conflict resolution.

What is the best way to clean up accumulated completed OpenSpec changes?▼

The best way to clean up accumulated OpenSpec changes is batch-archiving them together. This approach handles multiple completed items simultaneously, resolves overlapping delta specs, and preserves metadata in date-stamped directories.

Does batch-archiving OpenSpec changes require validating their state first?▼

Validating the state of completed OpenSpec changes is required before batch-archiving. The process ensures only completed items are processed, allowing the batch operation to safely handle conflicts and preserve metadata during archival.