openspec-bulk-archive-change

Archive multiple completed openspec changes with conflict resolution and status validation.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/runecalico-ai/second_edition_spellbook --skill openspec-bulk-archive-change-runecalico-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/runecalico-ai/second_edition_spellbook/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/runecalico-ai/second_edition_spellbook --skill openspec-bulk-archive-change-runecalico-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Batch Archiving: Archive several changes in a single operation.
  • Conflict Resolution: Automatically detects and resolves conflicts in capability specs by checking codebase implementation.
  • Status Validation: Verifies artifact status and task completion before archiving.
  • Use Case: When you have finished work on several related features (e.g., authentication, user profiles, and settings), you can use this skill to archive them all together, ensuring that any overlapping specifications are correctly merged or prioritized based on actual code.

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 instead of one by one?

To resolve spec conflicts during bulk archiving, the system automatically detects overlapping capability specifications and resolves them by checking the actual codebase implementation. This ensures that merged or prioritized specs accurately reflect the final code state.

What is validated before archiving completed changes in version control?

Before archiving completed changes, the system validates artifact status and task completion to ensure all work is truly finished. This status validation prevents manual errors by verifying that every task within the change set is complete before execution.

Do I need the openspec CLI to automate code archiving for multiple features?

Yes, you need the openspec CLI to automate code archiving for multiple features, as it provides the necessary commands for change listing, status checks, and synchronization. The CLI acts as the core engine for detecting and executing bulk archive operations.

Can I batch archive related features like authentication and user profiles together?

You can batch archive related features like authentication and user profiles together by grouping their completed changes into a single operation. The system intelligently handles any overlapping specifications between these features by analyzing the codebase implementation.