skills.rest
oalansilva
oalansilvaCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with conflict detection and status reports.

Updated Dec 28, 2025
Search Tags:#codebase#archive#conflict-resolution#openspec#bulk#delta-specs#history-management
One-click install
npx skills add https://github.com/oalansilva/crypto --skill openspec-bulk-archive-change-oalansilva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/oalansilva/crypto/tree/main/.codex/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/oalansilva/crypto --skill openspec-bulk-archive-change-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation.

Core Features & Use Cases

  • Batch-archive active changes by validating statuses and preparing a consistent archive history.
  • Detect and resolve delta-spec conflicts by inspecting the codebase to determine which changes are actually implemented.
  • Preserve configuration files and move archived changes to a date-stamped folder under openspec/changes/archive.
  • Generate a clear per-change status report and allow skipping incomplete changes when archiving.

Quick Start

Use the openspec bulk archive change skill to batch-archive all ready changes while preserving archive integrity.

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 OpenSpec changes in my codebase?▼

Batch archive completed OpenSpec changes by analyzing active changes, validating statuses, and moving them into date-stamped archive folders to ensure consistent codebase history management.

What is the best way to handle delta-spec conflicts when archiving multiple codebase changes?▼

Handle delta-spec conflicts by inspecting the codebase during bulk archival to detect which changes are actually implemented, allowing you to skip incomplete changes and ensure safe historical consistency.

Can I skip incomplete changes when doing a bulk archive of OpenSpec history?▼

Yes, you can skip incomplete changes during OpenSpec bulk archival. The process generates a per-change status report, allowing you to safely archive only completed changes while preserving configuration files.

Does archiving OpenSpec changes preserve the .openspec.yaml configuration file?▼

Yes, archiving OpenSpec changes preserves the .openspec.yaml file. It moves completed changes to an openspec/changes/archive/YYYY-MM-DD-<name> folder while maintaining the original configuration integrity.

Why does bulk archiving active changes require conflict resolution?▼

Bulk archiving requires conflict resolution to inspect the codebase and determine which changes are actually implemented. Detecting delta-spec conflicts prevents incomplete changes from corrupting historical consistency.

Related Skills

Explore More Software Engineering Skills→
sanfordzhangsanfordzhang
1

openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict-aware delta-spec handling.

Community
Advanced
jaxxstormjaxxstorm
4

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes into date-stamped directories.

Community
Advanced
belingudbelingud
30

openspec-archive-change

Archive completed OpenSpec changes with verified artifacts and delta specs.

Community
Advanced
DarkHighnessDarkHighness
11

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes into date-stamped directories.

Community
Advanced