openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with metadata and per-change reports.

2|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Yi-ming-Zhao/Fittin --skill openspec-bulk-archive-change-yi-ming-zhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/Yi-ming-Zhao/Fittin/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/Yi-ming-Zhao/Fittin --skill openspec-bulk-archive-change-yi-ming-zhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bulk-archives completed OpenSpec changes into an archival folder, reducing clutter in the change history and keeping the repository clean.

Core Features & Use Cases

  • Batch-archive multiple changes in a single operation.
  • Resolve delta-spec conflicts by inspecting the codebase and applying a deterministic order.
  • Preserve metadata and provide per-change status reporting for audits.

Quick Start

Select the changes you want to archive and confirm the bulk 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 OpenSpec changes at once without doing it one by one?

To bulk-archive OpenSpec changes, select the completed changes and confirm the batch operation. The process validates status and conflict evidence, then moves them into an archival folder with per-change reporting, eliminating manual per-change steps.

What is the best way to resolve delta-spec conflicts during a bulk archive operation?

Resolving delta-spec conflicts during bulk archival involves inspecting the codebase and applying a deterministic order. This ensures changes are archived safely without conflicts, preserving metadata and repository history across the batch.

Does bulk archiving OpenSpec changes preserve metadata for audit purposes?

Yes, bulk archiving OpenSpec changes preserves metadata and provides per-change status reporting for audits. This keeps the repository clean while ensuring historical data remains accessible across multi-change operations.

Can I archive OpenSpec changes if they have unresolved conflicts or incomplete statuses?

No, the bulk archival process validates status and conflict evidence before proceeding. Changes must be completed and conflict-free to be safely batch-archived, preventing the loss of unresolved codebase modifications.

When should I use a bulk archive for change management instead of manual archival?

Use bulk archival for change management when you have multiple completed OpenSpec changes cluttering your history. It reduces clutter and preserves history safely across multi-change operations without requiring manual per-change steps.