openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: jeffbalagosa

Archive multiple completed OpenSpec changes into a dated directory.

1|Updated May 22, 2022

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

Ready to run

npx skills add https://github.com/jeffbalagosa/pick-or-shuffle --skill openspec-bulk-archive-change-jeffbalagosa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/jeffbalagosa/pick-or-shuffle/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/jeffbalagosa/pick-or-shuffle --skill openspec-bulk-archive-change-jeffbalagosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation to streamline change management and keep histories intact.

Core Features & Use Cases

Batch-archive multiple openspec changes while preserving configuration and creating date-stamped archives.
Resolve delta spec conflicts by analyzing the codebase and applying in the correct order.
Ensure safe archival with options to preserve .openspec.yaml and handle partial failures gracefully.

Quick Start

Run the batch archive on all ready OpenSpec changes.

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

Bulk archiving completed changes involves selecting ready openspec entries, verifying their implementation status, and moving them to a date-stamped directory. This ensures only implemented specs are synchronized and preserves configuration files like .openspec.yaml.

How does bulk archiving handle delta spec conflicts?▼

When bulk archiving encounters delta spec conflicts, it analyzes the codebase to determine the correct application order. This prevents synchronization errors and ensures only implemented specs are archived.

Can I preserve my .openspec.yaml configuration when archiving changes?▼

The bulk archive operation includes options to preserve your .openspec.yaml file. It also handles partial failures gracefully, ensuring that a single error does not corrupt the entire batch archive.

What happens if some changes fail during a batch archive operation?▼

The tool handles partial failures gracefully during batch archiving, reporting outcomes for each change. It ensures that only implemented specs are synchronized and moved, while preserving your .openspec.yaml configuration.

When should I use a bulk archive for change management instead of archiving individually?▼

Bulk archiving is best when you need to streamline change management for multiple completed specs at once. It automates status checks, conflict resolution, and date-stamped archival, saving time compared to individual processing.