openspec-bulk-archive-change

Batch-archive completed OpenSpec changes while resolving delta-spec conflicts.

Updated Feb 5, 2026

Search Tags:#automation #codebase #CLI #archive #OpenSpec #conflict-resolution #bulk-operations

Ready to run

npx skills add https://github.com/arestivo/qoodle --skill openspec-bulk-archive-change-arestivo

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies batch archiving of completed OpenSpec changes by orchestrating a single, reliable workflow that minimizes manual steps and errors.

Core Features & Use Cases

Batch-archive multiple completed changes in one operation.
Detect and resolve delta-spec conflicts by inspecting the codebase before archiving.
Prompt users to select changes (no auto-selection) and confirm the final action.
Archive changes to openspec/changes/archive/YYYY-MM-DD-<name>, preserving the original .openspec.yaml.

Quick Start

Use this skill to batch-archive completed OpenSpec changes. When activated, it will list active changes, prompt you to select one or more changes (no auto-select), analyze artifact states, and resolve conflicts before archiving.

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 instead of one by one?▼

You can batch-archive multiple OpenSpec changes by selecting them from a list of active changes, allowing you to complete the archiving process in a single operation rather than handling each change individually.

Does batch archiving OpenSpec changes check for delta-spec conflicts?▼

Yes, batch archiving detects and resolves delta-spec conflicts by inspecting the codebase before archiving. This ensures that completed changes are safely moved without causing inconsistencies in your project.

Where do archived OpenSpec changes get stored and are configurations preserved?▼

Archived OpenSpec changes are stored in the openspec/changes/archive/YYYY-MM-DD-<name> directory. The archiving process preserves the original .openspec.yaml configuration files within the archived structure.

Do I need the OpenSpec CLI to run batch archive operations?▼

Yes, you need the OpenSpec CLI installed to run batch archive operations. The tool requires the CLI to interact with the codebase, list active changes, and execute the archiving workflow.

Can I auto-select all completed OpenSpec changes for batch archiving?▼

No, auto-selection is not supported for batch archiving OpenSpec changes. The tool prompts you to manually select one or more changes and requires you to confirm the final action to prevent accidental data loss.