openspec-bulk-archive-change

Archive multiple completed changes and resolve spec conflicts via codebase analysis.

1|Updated Feb 11, 2026

Search Tags:#git #version control #archiving #conflict resolution #change management #openspec

Ready to run

npx skills add https://github.com/vidos-id/usecase-demos --skill openspec-bulk-archive-change-vidos-id

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/vidos-id/usecase-demos/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/vidos-id/usecase-demos --skill openspec-bulk-archive-change-vidos-id

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes by intelligently handling potential conflicts and ensuring a clean, organized state.

Core Features & Use Cases

Batch Archiving: Archive several completed changes in a single operation, saving significant time and effort.
Conflict Resolution: Automatically detects and resolves conflicts between changes that affect the same capabilities by analyzing codebase implementations.
Use Case: When you have finished developing several features related to authentication and API endpoints, use this Skill to archive them all simultaneously, ensuring that any overlapping specifications are correctly merged or prioritized based on their implementation status and creation date.

Quick Start

Use the openspec bulk archive change skill to archive all completed 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 git changes at once?▼

Batch archiving completed changes allows you to select multiple finished features, automatically resolve overlapping spec conflicts by analyzing codebase implementations, and execute the archive operation in a single transaction.

How does conflict resolution work when archiving overlapping changes?▼

Conflict resolution works by analyzing codebase implementations to detect and resolve conflicts between changes affecting the same capabilities, correctly merging or prioritizing specifications based on their implementation status and creation date.

What is the best way to handle version control spec conflicts for completed features?▼

The best way to handle version control spec conflicts is to use agentic conflict resolution that analyzes artifact status, task completion, and delta spec validation to intelligently merge overlapping specifications during a batch archive operation.

Can I batch archive changes that modify the same capabilities in my codebase?▼

Yes, you can batch archive changes that modify the same capabilities because the process intelligently detects overlapping specifications and resolves them by analyzing your actual codebase implementations and their completion status.

When should I batch archive changes instead of archiving them individually?▼

You should batch archive changes instead of archiving individually when you have finished developing several related features, such as authentication and API endpoints, saving significant time and effort while ensuring a clean organized state.