openspec-bulk-archive-change

Batch-archive multiple completed changes and resolve spec conflicts via codebase checks.

5|2|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/syifan/cgra-flow-ui --skill openspec-bulk-archive-change-syifan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/syifan/cgra-flow-ui/tree/main/.github/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/syifan/cgra-flow-ui --skill openspec-bulk-archive-change-syifan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of archiving multiple completed changes simultaneously, saving time and reducing manual errors.

Core Features & Use Cases

  • Batch Archive: Archive multiple changes in a single operation.
  • Conflict Detection and Resolution: Handles spec conflicts by checking the codebase.
  • Status Display: Shows a summary of all changes before confirming the batch operation.

Quick Start

Archive all completed changes using the 'openspec-bulk-archive-change' skill.

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

You can batch-archive multiple completed changes in a software repository simultaneously using openspec-bulk-archive-change, which processes them in a single operation and displays a summary status before confirming the batch archive.

How does batch archiving handle spec conflicts in a codebase?

Batch archiving handles spec conflicts by analyzing the codebase for actual implementations, checking that completed changes are properly implemented before resolving conflicts and proceeding with the archive operation.

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

Yes, you need the openspec CLI installed and available, as the batch archive skill requires it to check the codebase for actual implementations and manage the archiving of completed changes.

Can I review changes before confirming a batch archive operation?

Yes, the skill shows a summary status display of all changes before confirming the batch operation, allowing you to review what will be archived and ensuring no manual errors occur during codebase change management.

What's the best way to manage change archiving for a large software repository?

Batch-archiving multiple completed changes through codebase analysis and conflict resolution is the best way to manage large repositories, as it reduces manual errors and saves time by processing changes in one operation.

Why does batch archiving check the codebase before archiving changes?

Batch archiving checks the codebase for actual implementations before archiving to ensure completed changes are truly implemented, which allows the skill to resolve spec conflicts accurately and prevent archiving incomplete work.