openspec-bulk-archive-change

Bulk-archive OpenSpec changes into a date-named directory while preserving .openspec.yaml.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/manishsinghmf/blink-with-anti --skill openspec-bulk-archive-change-manishsinghmf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/manishsinghmf/blink-with-anti/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/manishsinghmf/blink-with-anti --skill openspec-bulk-archive-change-manishsinghmf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive bulk completed changes in OpenSpec to simplify release hygiene and history preservation.

Core Features & Use Cases

  • Batch-archive changes in a single operation to consolidate change histories.
  • Detect and resolve conflicts by inspecting delta specs and the codebase, applying results in a deterministic order.
  • Preserve important metadata (e.g., .openspec.yaml) while moving changes to an archive directory named with the current date.
  • Use in multi-developer environments to safely move completed work into an archival store for audits.

Quick Start

Run the bulk archive command to move selected changes to an archive directory named with the current date.

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 OpenSpec changes to simplify release hygiene?

To bulk-archive OpenSpec changes, run the bulk archive command to move selected changes to a date-named archive directory. This consolidates change histories and preserves important metadata like .openspec.yaml during the move.

How does bulk archiving handle conflicts in multi-developer OpenSpec workflows?

Bulk archiving handles conflicts by inspecting delta specs and the codebase, then applying results in a deterministic order. This ensures reproducible archival steps in parallel and multi-user workflows.

What is the best way to preserve .openspec.yaml metadata when moving completed changes?

The best way to preserve .openspec.yaml metadata is using bulk archiving, which maintains important configuration while moving completed work into an archival store named with the current date for audits.

Can I batch-archive multiple OpenSpec changes in a single operation?

Yes, you can batch-archive multiple OpenSpec changes in a single operation. This streamlines change-history management by consolidating change histories and moving completed work for audits.

Does OpenSpec bulk archiving support timestamped directories for reproducible archival steps?

Yes, OpenSpec bulk archiving supports timestamped directories by moving changes to an archive directory named with the current date. This ensures reproducible archival steps for audit purposes.

When should I use bulk archiving instead of individual change archival in OpenSpec?

Use bulk archiving when consolidating change histories in multi-developer environments. It safely moves completed work into an archival store, handling conflict detection and per-change metadata for audits.