skills.rest
moogah
moogahCOMMUNITY
Explore all skills by this author →
GitHub

opsx-bulk-archive

Archive multiple completed changes with conflict resolution into date-stamped folders.

Updated Jan 20, 2026
Search Tags:#codebase#archive#conflict-resolution#openspec#change-management#bulk-archive#spec-sync
One-click install
npx skills add https://github.com/moogah/emacs --skill opsx-bulk-archive-moogah
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opsx-bulk-archive
Source: https://github.com/moogah/emacs/tree/main/.claude/skills/opsx-bulk-archive
Command: npx skills add https://github.com/moogah/emacs --skill opsx-bulk-archive-moogah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes at once. Use when archiving several parallel changes, with intelligent spec conflict resolution by checking the codebase for implementation evidence.

Core Features & Use Cases

  • Batch-archive changes with automatic spec conflict detection and resolution across multiple changes.
  • Validate artifact and task status for each change before archiving.
  • Archive each change into a date-stamped folder under openspec/changes/archive while preserving metadata.

Quick Start

Select the active changes to archive and confirm the operation to move each change into a date-stamped archive folder.

Frequently Asked Questions about opsx-bulk-archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive multiple completed changes in openspec at once?▼

Bulk-archiving completed changes requires selecting active changes to archive, confirming the operation, and letting the workflow validate artifact statuses before moving each change into a date-stamped archive folder preserving the original .openspec.yaml.

How does spec conflict resolution work when archiving parallel changes?▼

Spec conflict resolution works by evaluating active changes and their specs, checking the codebase for implementation evidence, and deterministically syncing specs to resolve conflicts before archiving parallel changes.

When do I need to batch-archive changes with conflict checks?▼

You need to batch-archive changes with conflict checks when archiving several parallel changes simultaneously that require intelligent spec conflict detection and deterministic spec syncing across multiple changes.

Can I preserve the original .openspec.yaml metadata when archiving changes?▼

Yes, the bulk-archive workflow preserves the original .openspec.yaml metadata by moving each completed change into a date-stamped archive folder under openspec/changes/archive/YYYY-MM-DD-<name>.

What is validated before a change is moved to the archive folder?▼

Before archiving, the workflow validates artifact and task status for each change to ensure only completed changes are moved into the date-stamped archive folder.

Related Skills

Explore More Software Engineering Skills→
Charles5277Charles5277
45

openspec-bulk-archive-change

Archive multiple completed openspec changes and resolve delta-spec conflicts.

Community
Advanced
agentxmagentxm
5

openspec-archive-change

Archive completed OpenSpec changes to dated directories with delta-spec synchronization.

Official
Intermediate
harqianharqian
1

openspec-bulk-archive-change

Archive multiple completed code changes using the openspec CLI.

Community
Advanced
daodaoedudaodaoedu

openspec-bulk-archive-change

Archive multiple OpenSpec changes with conflict detection and spec syncing.

Official
Advanced