openspec-bulk-archive-change

Consolidate completed OpenSpec changes into a dated archive directory.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/whatevertogo/Astrcode --skill openspec-bulk-archive-change-whatevertogo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/whatevertogo/Astrcode/tree/main/.codex/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/whatevertogo/Astrcode --skill openspec-bulk-archive-change-whatevertogo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bulk archiving of multiple OpenSpec changes to keep history organized and reduce repetitive manual operations.

Core Features & Use Cases

  • Bulk archiving: Move multiple completed changes into a dated archive path with guardrails to avoid overwriting existing archives.
  • Detect and resolve delta-spec conflicts before archiving.
  • Preserve existing configuration and ensure only ready changes are archived.

Quick Start

Select the active changes to archive, review the consolidated plan, and confirm to move matches into archive/YYYY-MM-DD-<name>.

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

You can bulk-archive completed OpenSpec changes by consolidating them into a single dated archive directory, allowing batch selection of ready changes to move together safely.

What is the best way to handle delta-spec conflicts before archiving changes?

Resolving delta-spec conflicts is a required step before archiving changes, ensuring that only ready changes without conflicts are moved into the dated archive path.

How does bulk archiving preserve existing OpenSpec configuration?

Bulk archiving preserves existing configuration by moving only the selected completed changes into a dated archive path while leaving the active project configuration untouched.

Can I select specific active changes to archive and leave others behind?

Yes, the bulk archive process lists active changes and their statuses, letting you select specific ready changes to archive while leaving incomplete ones in place.

What happens if an archive directory with the same date already exists?

The bulk archival process includes guardrails to avoid overwriting existing archives, moving selected changes into a dated archive path without destroying prior data.

Do I need to confirm before changes are moved to the archive?

Yes, the process enforces obtaining user confirmation by presenting a consolidated plan before performing the archival move of the selected changes.