openspec-bulk-archive-change

Batch-archive multiple completed OpenSpec changes with conflict detection.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/LippyyDev/Agate-Antigravity-Helper- --skill openspec-bulk-archive-change-lippyydev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/LippyyDev/Agate-Antigravity-Helper-/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/LippyyDev/Agate-Antigravity-Helper- --skill openspec-bulk-archive-change-lippyydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-archives multiple completed openspec changes in a single operation to clean up active workspaces and centralize change history.

Core Features & Use Cases

  • Batch-select and archive multiple changes that are completed
  • Detect and resolve delta-spec conflicts across changes before archiving
  • Preserve archival structure with date-based directories and per-change metadata

Quick Start

Choose the changes you want to archive and confirm to start the bulk archive process.

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 instead of moving them one by one?▼

You can bulk-archive multiple completed OpenSpec changes in a single operation to clean up active workspaces, using interactive selection and a final confirmation to manage the batch process efficiently.

How does bulk archiving handle delta-spec conflicts across multiple OpenSpec changes?▼

Bulk archiving detects delta-spec conflicts across selected changes before moving them, allowing you to resolve inconsistencies interactively and optionally synchronize specs to ensure a clean archival state.

What is the directory structure used when archiving completed OpenSpec changes?▼

Archived OpenSpec changes are moved into date-based directories named archive/YYYY-MM-DD-<name>, preserving original change metadata and centralizing the change history for future reference.

Can I review the status of each change before confirming a bulk archive operation?▼

Yes, the bulk archive workflow provides per-change status reporting during selection, requiring a final confirmation before moving any records to ensure you verify each item's readiness.

What happens to original OpenSpec change files after they are bulk-archived?▼

Original changes are preserved while their records are moved to date-based archive directories, keeping the active workspace clean without losing any change history or metadata.

When should I use a bulk archive operation for OpenSpec changes instead of individual archiving?▼

Bulk archiving is applicable when several completed changes need to be archived at once, reducing manual overhead and ensuring consistent conflict detection across delta specs during cleanup.