openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with conflict detection and spec synchronization.

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/ValorVie/settingZsh --skill openspec-bulk-archive-change-valorvie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/ValorVie/settingZsh/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/ValorVie/settingZsh --skill openspec-bulk-archive-change-valorvie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving completed OpenSpec changes one at a time is tedious, and archiving several parallel changes risks spec conflicts when multiple changes touch the same capability. This Skill batch-archives changes while detecting and resolving spec conflicts by inspecting the actual codebase. ## Core Features & Use Cases - Batch Archiving: Select and archive multiple active changes in a single operation, moving them to dated archive directories. - Conflict Detection & Resolution: Detects when 2+ changes modify the same capability spec, then checks the codebase to determine which changes are actually implemented and applies specs in chronological order. - Status Reporting: Shows a consolidated table of artifact status, task completion, delta specs, and conflicts before confirming the batch operation. - Use Case: After finishing a sprint with five parallel feature changes, select all of them, review the conflict analysis for the shared auth spec, and archive everything in one confirmed operation. ## Quick Start Ask the assistant to bulk archive all completed OpenSpec changes and resolve any spec conflicts automatically.

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?▼

Run the bulk archive workflow, which lists active changes via openspec list, prompts you to multi-select changes, validates their status, and moves each to openspec/changes/archive/YYYY-MM-DD-<name> after syncing delta specs.

How are spec conflicts resolved when archiving parallel changes?▼

When two or more changes touch the same capability spec, the workflow reads each delta spec and searches the codebase for implementation evidence. If both are implemented, specs apply in chronological order; if only one is implemented, only that one syncs.

What happens if a change has incomplete tasks during bulk archive?▼

Incomplete changes are flagged in the status table with warnings showing unfinished artifacts and tasks. You can choose to archive only ready changes, archive everything with warnings, or cancel the operation.

Does bulk archive require the openspec CLI?▼

Yes, the workflow requires the openspec CLI to list active changes and retrieve artifact status via openspec list --json and openspec status --change commands. Without it, change discovery and validation cannot run.

What happens if the archive target directory already exists?▼

If the dated archive directory for a change already exists, that specific change fails with an error while the remaining changes continue archiving. The final summary reports all successes, skips, and failures.