openspec-bulk-archive-change

Archive completed codebase changes in batches with conflict resolution.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/kamansoft/vite-plugin-flatwave-react --skill openspec-bulk-archive-change-kamansoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/kamansoft/vite-plugin-flatwave-react/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/kamansoft/vite-plugin-flatwave-react --skill openspec-bulk-archive-change-kamansoft

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes in a codebase, reducing the time and complexity involved in manual archiving.

Core Features & Use Cases

  • Batch Archiving: Archive multiple changes together, reducing the manual effort required.
  • Conflict Resolution: Handles spec conflicts intelligently by checking the codebase.
  • Status Checking: Provides a comprehensive status table of changes before confirming the archive operation.
  • User Confirmation: Allows users to choose which changes to archive and confirm the batch operation.
  • Archive Execution: Executes the archive operation for each confirmed change, with detailed outcome tracking.
  • Use Case: Ideal for teams with multiple parallel changes in a codebase who need to archive completed work efficiently.

Quick Start

Archive all completed changes in the current codebase by running the 'archive_changes' skill command.

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 a codebase at once?

Batch archiving of completed changes is automated by analyzing implementation status and archiving selected changes together with detailed tracking of artifacts, tasks, and specs.

How does batch archiving handle spec conflict resolution?

Spec conflict resolution during batch archiving is handled by checking the codebase's implementation status, ensuring changes are archived accurately based on actual code state.

Do I need openspec-cli to batch archive codebase changes?

Yes, openspec-cli is required as a dependency to run the scripts that automate the batch archiving operation and resolve spec conflicts in your codebase.

What is the best way to track artifacts and tasks when archiving changes?

Tracking artifacts and tasks during archiving is managed by the batch operation, which executes archives for confirmed changes and provides a detailed outcome tracking table.

Can I choose which completed changes to include in a batch archive operation?

Yes, user confirmation is supported by providing a comprehensive status table of changes before execution, allowing you to select which changes to archive in the batch operation.

When should I avoid batch archiving changes in my codebase?

Avoid batch archiving when changes are not fully completed or spec conflicts remain unresolved, as the process relies on checking implementation status to ensure accurate archiving.