Verified:GitHub

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes into date-stamped directories.

11|3|Updated Dec 20, 2025

Search Tags:#conflict-resolution #openspec #workflow-automation #changes #version-control #codebase-analysis #bulk-archive

Ready to run

npx skills add https://github.com/DarkHighness/coi-public --skill openspec-bulk-archive-change-darkhighness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/DarkHighness/coi-public/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/DarkHighness/coi-public --skill openspec-bulk-archive-change-darkhighness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed OpenSpec changes in a single operation.

Core Features & Use Cases

Batch selection and validation of active changes
Conflict detection and automated resolution guidance
Safe archiving with date-stamped archive folders and preserved metadata
Spec synchronization when possible

Quick Start

Archive all eligible changes now.

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 batch archive completed OpenSpec changes in a single operation?▼

Batch archive completed OpenSpec changes by selecting multiple active changes, detecting conflicts, and moving them into date-stamped archive directories while preserving metadata.

What is the best way to handle change conflicts when archiving OpenSpec changes?▼

Handle change conflicts during batch archival through automated conflict detection and resolution guidance that ensures safe movement of active changes into the archive.

Do I need a specific project layout to batch archive OpenSpec changes?▼

Batch archiving OpenSpec changes requires the openspec/changes project layout and a local CLI with permissions to move changes into the archive while preserving metadata.

How does spec synchronization work when batch archiving OpenSpec changes?▼

Spec synchronization during batch archival attempts to synchronize specs when possible after selecting, validating, and resolving conflicts for active OpenSpec changes.

Why does batch archiving OpenSpec changes require date-stamped archive folders?▼

Date-stamped archive folders ensure safe archival by organizing batch-processed OpenSpec changes chronologically while preserving their original metadata during the move.

Can I archive all eligible OpenSpec changes at once without manual selection?▼

Archive all eligible OpenSpec changes at once through batched selection and validation that automatically filters active changes, detects conflicts, and safely moves them into the archive.