openspec-bulk-archive-change

Archive multiple completed changes while resolving spec conflicts via codebase inspection.

2|Updated Feb 25, 2026

Search Tags:#git #version control #specifications #code management #archiving #openspec

Ready to run

npx skills add https://github.com/yandiaan/adis-ai --skill openspec-bulk-archive-change-yandiaan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/yandiaan/adis-ai/tree/main/.qoder/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/yandiaan/adis-ai --skill openspec-bulk-archive-change-yandiaan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes by intelligently handling potential spec conflicts and user confirmations, preventing manual errors and saving significant time.

Core Features & Use Cases

Batch Archiving: Archive several completed changes in a single operation.
Conflict Resolution: Automatically detects and resolves conflicts between changes touching the same capability specs by analyzing codebase implementations.
User-Guided Workflow: Prompts the user for selections and confirmations at critical steps, ensuring user control.
Use Case: When you have finished developing several related features, use this skill to archive them all efficiently, ensuring that their specifications are correctly merged or prioritized based on actual code implementation.

Quick Start

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

To archive multiple completed changes at once, this skill concurrently processes batch archives and resolves spec conflicts by inspecting the codebase for implementation evidence. It prompts for user selections and confirmations to ensure safe operations.

How does bulk archiving resolve specification conflicts for the same capabilities?▼

Bulk archiving resolves specification conflicts by inspecting the codebase for actual implementation evidence. It analyzes the code to correctly merge or prioritize specs based on what was actually built, prompting you for confirmations at critical steps.

Do I need the openspec CLI to batch archive completed code changes?▼

Yes, you need the openspec CLI to batch archive completed code changes. The CLI is required for listing changes, checking statuses, and synchronizing specifications during the concurrent archiving workflow.

What is the best way to merge specifications for several related features after development?▼

The best way to merge specifications for related features is batch archiving completed changes concurrently. This approach intelligently handles potential spec conflicts by analyzing codebase implementations, preventing manual errors and saving time.

Can I review and select which completed changes to archive in a batch operation?▼

Yes, you can review and select which completed changes to archive. The workflow prompts the user for selections and confirmations at critical steps, ensuring you maintain control over which changes are included in the batch operation.