openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict-aware delta preservation.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/rockdong/stock_for_cpp --skill openspec-bulk-archive-change-rockdong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/rockdong/stock_for_cpp/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/rockdong/stock_for_cpp --skill openspec-bulk-archive-change-rockdong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes in bulk to reduce manual overhead and keep the change history clean, especially when handling parallel changes.

Core Features & Use Cases

  • Batch-archive multiple completed changes in a single operation, preserving history and OpenSpec structure.
  • Resolve delta spec conflicts by inspecting the codebase and applying deterministic resolutions.
  • Preserve the .openspec.yaml file when moving changes to the archive to maintain metadata consistency.
  • Provide clear visibility into statuses, conflicts, and outcomes prior to archiving to support auditable workflows.

Quick Start

Select the changes to archive, then run the bulk archive operation to move them into the archive directory with a date-prefixed path.

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?

To batch-archive multiple OpenSpec changes, select the completed changes and run a bulk archive operation to move them into an archive directory using a date-prefixed path while preserving delta specs and metadata.

How does bulk archiving handle delta spec conflicts in OpenSpec?

Bulk archiving resolves delta spec conflicts by inspecting the codebase and applying deterministic resolutions, providing visibility into statuses and outcomes before archiving to ensure codebase integrity.

What is the best way to manage OpenSpec change history for parallel changes?

The best way to manage parallel OpenSpec change history is batch-archiving completed changes to reduce manual overhead, enforcing conflict-aware archiving while preserving the .openspec.yaml metadata file for consistency.

Does OpenSpec bulk archiving preserve the .openspec.yaml file when moving changes?

Yes, OpenSpec bulk archiving preserves the .openspec.yaml file when moving changes to the archive directory, ensuring metadata consistency and maintaining the structural integrity of the change history.

What happens when archiving conflicts cannot be resolved during OpenSpec bulk operations?

When OpenSpec bulk archiving conflicts cannot be resolved through codebase inspection, the system provides a safe fallback mechanism to prevent data corruption and maintains clear visibility into unresolved statuses.

Can I use bulk archive operations for OpenSpec changes with multiple parallel branches?

Yes, bulk archive operations are designed for scenarios with multiple parallel OpenSpec changes, applying conflict-aware archiving with date-stamped paths to streamline change management while ensuring codebase integrity.