openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict resolution based on codebase evidence.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-bulk-archive-change-guillaumejay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/guillaumejay/FileIndexer/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-bulk-archive-change-guillaumejay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed changes across multiple work items is error-prone and time-consuming. This skill batch-archives changes and resolves conflicts intelligently by inspecting the codebase to determine what is actually implemented.

Core Features & Use Cases

  • Interactive selection: choose one or more changes, including an "All changes" option.
  • Conflict-aware archiving: detects overlapping delta specs across selected changes and resolves them using codebase evidence.
  • Metadata preservation: preserves .openspec.yaml and related metadata during archiving.
  • Automated audit trails: records the outcome of each archived change for traceability.

Quick Start

Archive multiple changes by selecting them, then confirm to proceed.

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 completed changes in OpenSpec without causing delta spec conflicts?

Batch-archive completed changes by interactively selecting them, allowing the system to evaluate delta specs and check the codebase for implementation evidence to intelligently resolve conflicts during the archiving process.

What happens when multiple OpenSpec changes have overlapping delta specs during archiving?

When overlapping delta specs are detected across selected changes, conflict-aware archiving inspects the codebase to determine what is actually implemented and resolves the conflicts automatically using that evidence.

Do I need the OpenSpec CLI to archive multiple changes at once?

Yes, you need the OpenSpec CLI installed to batch-archive changes, as the workflow processes active changes, evaluates delta specs, checks for codebase implementation evidence, and preserves metadata like .openspec.yaml.

How does archiving changes affect OpenSpec metadata like .openspec.yaml?

Archiving changes preserves your .openspec.yaml and related metadata entirely, ensuring no configuration is lost while generating automated audit trails to record the outcome of each archived change for traceability.

Can I select all active changes for archiving simultaneously in OpenSpec?

Yes, you can interactively select one, multiple, or all active changes at once using the "All changes" option, then confirm your selection to proceed with batch archiving.

How do I verify codebase implementation evidence before archiving OpenSpec changes?

The batch-archive process automatically evaluates delta specs and checks for implementation evidence directly in your codebase before archiving your chosen changes, ensuring only completed work is archived.