openspec-bulk-archive-change

Archive multiple completed OpenSpec changes by moving directories into an archive path.

9|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/fjpulidop/specrails-core --skill openspec-bulk-archive-change-fjpulidop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/fjpulidop/specrails-core/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/fjpulidop/specrails-core --skill openspec-bulk-archive-change-fjpulidop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes at once to streamline release hygiene and reduce manual work.

Core Features & Use Cases

  • Batch-select active changes using the OpenSpec CLI and move them into an archive directory
  • Detect and resolve delta-spec conflicts by consulting the codebase and applying chronological order
  • Generate consolidated status reports and confirmations before executing the archive

Quick Start

Select the active changes to archive and confirm to execute the bulk archive operation.

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 completed OpenSpec changes at once?

You can bulk-archive multiple completed OpenSpec changes by batch-selecting active changes and moving their directories into an archive path in a single operation. The process evaluates artifacts, tasks, and specs for each selected change.

How are delta-spec conflicts resolved during a bulk archive?

Delta-spec conflicts are detected and resolved by consulting the codebase and applying resolutions in chronological order. This ensures that overlapping changes are processed sequentially and safely.

Does bulk archiving changes require the OpenSpec CLI?

Yes, the OpenSpec CLI is required to batch-select active changes and execute the bulk archive operation. The process also validates and preserves the .openspec.yaml file throughout.

What happens if there are errors during a batch archive of codebase changes?

Comprehensive progress and error handling are provided throughout the batch process. A consolidated status report is generated and presented to the user for confirmation before executing the archive.

Can I review the status of my changes before committing to a bulk archive?

Yes, the skill generates consolidated status reports and confirmations before executing the archive operation. This allows you to review all selected changes and detected conflicts prior to commitment.

When should I use bulk archiving instead of archiving changes individually?

Bulk archiving is ideal for streamlining release hygiene and reducing manual work when you have multiple completed changes. It safely processes delta-spec conflicts chronologically across all selected changes.