openspec-bulk-archive-change

Archive multiple completed openspec changes and resolve spec conflicts in one operation.

Updated Apr 15, 2026

Search Tags:#automation #cli #conflict-resolution #openspec #change-management #bulk-archive

Ready to run

npx skills add https://github.com/caelaxie/agenthub --skill openspec-bulk-archive-change-caelaxie

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/caelaxie/agenthub/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/caelaxie/agenthub --skill openspec-bulk-archive-change-caelaxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually archiving many completed openspec changes is time‑consuming and prone to errors, especially when multiple changes modify the same specs and create conflicts.

Core Features & Use Cases

Batch archiving: Archive several completed changes in one operation.
Spec conflict detection: Identify and resolve overlapping spec modifications before archiving.
Automated status checks: Gather artifact statuses, task completion, and delta spec details for each change.
User‑guided selection: Multi‑select interface lets users pick which changes to archive.
Safety guards: Prevents accidental archiving of incomplete changes and warns about potential issues.

Quick Start

Ask the assistant to bulk archive the selected changes using the openspec‑bulk‑archive‑change skill.

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 bulk archive openspec changes, you need the openspec CLI installed and shell access to read the changes directory. The skill gathers artifact statuses and task details, then moves completed files automatically.

How does bulk archiving handle spec conflicts from parallel changes?▼

Bulk archiving detects overlapping spec modifications before moving files, identifying conflicts from parallel changes and guiding you through resolution to prevent archive errors.

Can I archive incomplete changes using the openspec CLI?▼

No, safety guards check artifact statuses and task completion details to prevent accidental archiving of incomplete changes, warning about potential issues before moving any files.

What's the best way to manage batch archiving when multiple changes modify the same specs?▼

The best way is using automated conflict detection that reviews delta spec details and prevents errors by resolving overlapping modifications before executing the batch archive move.

Why does batch archiving openspec changes fail when specs overlap?▼

Batch archiving fails because parallel changes create conflicting modifications in the same files. Detecting delta spec conflicts before moving ensures you resolve overlapping edits safely.