skills.rest
DataCovey
DataCoveyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Batch-archive multiple completed changes with conflict detection and dated folder organization.

27|2|Updated Jan 31, 2026
Search Tags:#automation#conflict-resolution#openspec#version-control#code-management#bulk-archive#spec-sync
One-click install
npx skills add https://github.com/DataCovey/nornweave --skill openspec-bulk-archive-change-datacovey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/DataCovey/nornweave/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/DataCovey/nornweave --skill openspec-bulk-archive-change-datacovey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation, reducing manual steps and minimizing human error.

Core Features & Use Cases

  • Batch archiving of multiple changes with conflict detection and resolution.
  • Preserves original change metadata and organizes archives under a date-stamped folder for auditability.
  • Supports optional spec synchronization guidance when changes touch overlapping capabilities.

Quick Start

Run the batch archive workflow to process all active changes and 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 bulk-archive completed changes without causing version-control conflicts?▼

Bulk-archiving completed changes requires batch processing with conflict detection and deterministic ordering. This approach archives multiple changes in a single operation, resolving conflicts based on delta specs while preserving original metadata.

What is the best way to archive multiple concurrent code changes safely?▼

Archiving multiple concurrent changes safely involves coordinated batch archiving with conflict resolution. The process enforces deterministic ordering and archives completed changes under a dated folder to maintain auditability.

How does spec synchronization work when archiving overlapping changes?▼

Spec synchronization during archiving provides optional guidance when concurrent changes touch overlapping capabilities. It uses delta specs to detect and resolve conflicts, ensuring coordinated archiving across multiple changes.

When do I need to batch-archive changes instead of archiving them individually?▼

Batch-archiving is needed for projects with concurrent changes requiring coordinated archiving. It reduces manual steps and minimizes human error compared to processing multiple completed changes individually.

Does bulk archiving preserve the original openspec configuration file?▼

Yes, bulk archiving preserves the original .openspec.yaml file. The process archives completed changes under a date-stamped folder while maintaining the original change metadata for auditability.

What happens if conflicting deltas are detected during batch archiving?▼

When conflicting deltas are detected during batch archiving, the process applies conflict resolution based on delta specs. It enforces deterministic ordering to safely archive multiple concurrent changes.

Related Skills

Explore More Software Engineering Skills→
guillaumejayguillaumejay

openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict resolution based on codebase evidence.

Community
Advanced
rafazafarrafazafar

openspec-archive-change

Archive completed OpenSpec changes to a date-stamped directory after validation.

Community
Advanced
VIethoangnguyenleVIethoangnguyenle

openspec-archive-change

Verify, synchronize, and archive completed workflow changes with the openspec CLI.

Community
Intermediate
pabloimrik17pabloimrik17

openspec-bulk-archive-change

Archive multiple openspec changes with conflict detection and resolution.

Community
Advanced