openspec-bulk-archive-change

Archive multiple completed changes and resolve spec conflicts by analyzing codebase implementations.

95|15|Updated Nov 25, 2025

Search Tags:#workflow #archive #batch #openspec #changes #spec conflicts

Ready to run

npx skills add https://github.com/jixoai/openspecui --skill openspec-bulk-archive-change-jixoai

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes simultaneously, especially when dealing with numerous parallel updates.

Core Features & Use Cases

Batch Archiving: Archive several changes in a single operation.
Conflict Resolution: Intelligently handles spec conflicts by analyzing the codebase.
Use Case: When you have finished work on several related features (e.g., authentication, user profiles, and permissions), you can use this skill to archive them all at once, ensuring spec consistency.

Quick Start

Use the openspec-bulk-archive-change skill to archive all completed changes after reviewing their status.

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 changes at once without causing spec conflicts?▼

Batch archiving multiple changes simultaneously is handled by validating artifact and task status first, then intelligently analyzing the codebase to detect and resolve capability conflicts before syncing specs.

What is the best way to resolve spec conflicts when archiving parallel feature updates?▼

Resolving spec conflicts during archiving involves analyzing codebase implementations to intelligently detect capability conflicts and resolve them agentically, ensuring spec consistency across parallel updates like authentication and permissions.

Can I select which active changes to include in a batch archive operation?▼

Yes, the batch archiving process lists active changes and prompts user selection, allowing you to specify exactly which completed updates to include in the single archive operation.

Does batch archiving changes validate task status before starting the operation?▼

Yes, validating artifact and task status is a prerequisite step before archiving changes, ensuring only fully completed work is processed and synced to prevent data inconsistencies.

Why does batch archiving fail when there are unresolved capability conflicts?▼

Batch archiving fails because unresolved capability conflicts threaten spec consistency; the system must detect and agentically resolve these conflicts by analyzing the codebase before it can safely perform the archiving operation.

When should I use batch archiving instead of archiving changes individually?▼

Batch archiving is ideal when you have finished work on several related features simultaneously, such as authentication and user profiles, allowing you to archive them all at once to maintain spec consistency efficiently.