openspec-bulk-archive-change

Archive multiple OpenSpec changes in a single batch while preserving metadata.

57|17|Updated May 5, 2025
One-click install
npx skills add https://github.com/jerome-benoit/freqai-strategies --skill openspec-bulk-archive-change-jerome-benoit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/jerome-benoit/freqai-strategies/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/jerome-benoit/freqai-strategies --skill openspec-bulk-archive-change-jerome-benoit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation.

Core Features & Use Cases

  • Batch-validate active changes, detect conflicts, and consolidate their specs.
  • Resolve overlapping delta specs by checking the codebase and applying conflicts in chronological order.
  • Confirm and execute the archive while preserving metadata and avoiding overwrites.

Quick Start

Select the active OpenSpec changes, review the suggested batch results, and confirm to initiate the archive.

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 in a single batch?

Batch-validate active OpenSpec changes, detect conflicts, and consolidate their specs in a single operation. The workflow includes selection, validation, conflict resolution, confirmation, and archival while keeping the .openspec.yaml file intact.

What happens when batch archiving overlapping delta specs in my codebase?

The batch operation detects conflicts in overlapping delta specs by checking the codebase and applies them in chronological order. This ensures overlapping changes are resolved systematically before executing the final archive without overwrites.

How does batch conflict resolution work for parallel OpenSpec changes?

Batch conflict resolution validates active parallel changes, detects overlapping delta spec conflicts, and resolves them chronologically. This workflow allows parallel changes to be archived together safely while preserving metadata and avoiding overwrites.

Does batch archiving OpenSpec changes overwrite existing metadata?

Batch archiving does not overwrite existing metadata. The end-to-end workflow is designed to preserve change metadata and keep the .openspec.yaml configuration file intact throughout the confirmation and archival process.

Can I archive parallel codebase changes that must be consolidated together?

Yes, the workflow applies specifically to parallel changes that must be archived together. It batch-validates active changes, detects conflicts, consolidates their specs, and executes the archive while preserving metadata.