openspec-bulk-archive-change

Archive multiple completed code changes using the openspec CLI.

1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/harqian/wifi-client --skill openspec-bulk-archive-change-harqian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/harqian/wifi-client/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/harqian/wifi-client --skill openspec-bulk-archive-change-harqian

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of archiving multiple completed changes at once, saving time and streamlining the management of parallel changes.

Core Features & Use Cases

  • Batch Archiving: Archive multiple changes in a single operation.
  • Conflict Detection: Intelligently detect and resolve spec conflicts across changes.
  • Codebase Verification: Ensure that changes are implemented before archiving.
  • Status Consolidation: Show a consolidated status table of all changes before archiving.
  • User Confirmation: Provide options for archiving all, ready, or none of the selected changes.
  • Archive Execution: Perform the archiving process for each confirmed change.
  • Summary Output: Display a final summary of the archived changes, skipped, and failed changes.

Quick Start

Use the openspec-bulk-archive-change skill to archive completed changes in a single operation.

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 batch archive multiple completed code changes at once?

Batch archiving of completed code changes is automated by processing multiple modifications in a single operation, streamlining project maintenance workflows and saving time when finalizing parallel development branches.

How does conflict resolution work when archiving parallel code changes?

Conflict resolution for archiving parallel code changes works by using intelligent code analysis to detect and resolve spec conflicts across modifications before final execution, ensuring codebase integrity during project maintenance.

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

You need the openspec CLI installed to use this batch archiving capability, as the automation relies on its command line interface to execute code versioning operations and verify implementations before archiving.

Can I review a status table before archiving code changes?

You can review a consolidated status table of all selected changes before archiving, with options to confirm archiving all, only ready, or none of the modifications based on the displayed codebase verification results.

What happens if a code change fails verification during batch archiving?

If a code change fails verification or execution during batch archiving, the process skips the failed item, continues archiving other confirmed changes, and displays a final summary separating archived, skipped, and failed modifications.