openspec-bulk-archive-change

Archive multiple completed changes and resolve spec conflicts against the codebase.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/dorrio/sorteo-app-generator --skill openspec-bulk-archive-change-dorrio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/dorrio/sorteo-app-generator/tree/main/.agent/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/dorrio/sorteo-app-generator --skill openspec-bulk-archive-change-dorrio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes simultaneously, especially when dealing with parallel development efforts, by intelligently handling spec conflicts.

Core Features & Use Cases

  • Batch Archiving: Archive several changes in a single operation.
  • Conflict Resolution: Automatically detects and resolves conflicts in specification files by checking the codebase for actual implementation.
  • Intelligent Syncing: Syncs specifications based on implementation status and chronological order when conflicts arise.
  • Use Case: When you have finished work on several related features (e.g., authentication and authorization updates), use this skill to archive them all at once, ensuring their specifications are correctly merged into the main branch.

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 changes in git at once?

To archive multiple completed changes simultaneously, you can batch confirm and execute archiving in a single operation. This process validates artifact status and task completion for selected changes before merging them into the main branch.

How does conflict resolution work for specification files during parallel development?

Conflict resolution for specification files works by validating against the codebase to find actual implementation evidence. It intelligently syncs specifications based on implementation status and chronological order to resolve conflicts from parallel development.

What is the best way to sync specifications based on implementation evidence?

The best way to sync specifications based on implementation evidence is by analyzing delta specs for selected changes. This ensures specification synchronization accurately reflects the actual codebase state during batch archiving.

Can I batch archive several related features without causing spec conflicts?

Yes, you can batch archive several related features without causing spec conflicts. The process automatically detects and resolves specification conflicts by checking the codebase for actual implementation and merging them chronologically.

Does batch archiving validate task completion before execution?

Yes, batch archiving validates task completion and artifact status before execution. It checks delta spec analysis for selected changes to ensure all completed work is properly confirmed prior to final archiving.