openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with conflict resolution and status reporting.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/rangechow/LotGameClient --skill openspec-bulk-archive-change-rangechow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/rangechow/LotGameClient/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/rangechow/LotGameClient --skill openspec-bulk-archive-change-rangechow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation to simplify maintenance and maintain a clean, auditable change history.

Core Features & Use Cases

  • Batch selection of active changes to archive
  • Automated conflict detection and resolution based on delta specs and codebase evidence
  • Comprehensive status reporting including artifact state, task completion, and delta specs
  • Optional consolidation of changes into an archive path with date stamping

Quick Start

Select the changes you want to archive and confirm the operation to begin the batch archive.

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 bulk archive completed changes in OpenSpec without manual conflicts?

Bulk archive completed OpenSpec changes by batch selecting active changes, running automated conflict analysis against delta specs and codebase evidence, and generating a consolidated archival report. The process validates artifact status and task completion before moving changes.

What does conflict resolution based on codebase evidence mean when archiving changes?

Conflict resolution during change archival analyzes delta specs and matches them against actual codebase evidence to automatically determine the correct resolution. This ensures archived changes accurately reflect the final state of the codebase without manual intervention.

Can I select multiple active OpenSpec changes for batch archival at once?

Yes, you can select multiple active OpenSpec changes for batch archival in a single operation. The system validates artifact status, task completion, and delta specs for all selected changes before processing the consolidated archival.

What is checked during status validation before archiving an OpenSpec change?

Status validation before archiving checks artifact states, verifies task completion, and reviews delta specs for the selected changes. This ensures only fully completed changes with resolved conflicts are consolidated into the archive path with date stamping.

How do I get a consolidated report after archiving multiple OpenSpec changes?

A consolidated report is automatically generated after the bulk archive operation completes. It details the archival outcome for each selected change, including conflict resolution results, artifact validation status, and task completion verification.