openspec-bulk-archive-change

Batch-archive multiple completed changes with conflict resolution via codebase inspection.

3|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/moltbook-experiments/glasshouse-protocol --skill openspec-bulk-archive-change-moltbook-experiments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/moltbook-experiments/glasshouse-protocol/tree/main/.github/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/moltbook-experiments/glasshouse-protocol --skill openspec-bulk-archive-change-moltbook-experiments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation to streamline batch archival and reduce manual overhead.

Core Features & Use Cases

  • Batch-archive multiple changes with conflict-aware handling by inspecting the codebase to determine what's actually implemented.
  • Resolve deltas across changes and archive in a reproducible, auditable history.
  • Use when you need to consolidate several parallel changes into a single archived record for project hygiene.

Quick Start

Select the active changes to archive and confirm the batch 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 completed codebase changes in openspec?

Batch archiving changes consolidates multiple completed codebase updates into a single archived record by inspecting the codebase to determine what is actually implemented, preserving an auditable history.

How does bulk archive handle spec conflicts across multiple changes?

Bulk archive handles spec conflicts by inspecting the codebase to determine what is actually implemented across changes, resolving deltas automatically to ensure a reproducible and auditable historical record.

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

Yes, the openspec CLI is required to perform batch archival of changes, as the operation depends on its codebase inspection and conflict resolution mechanisms to accurately consolidate deltas.

When should I use batch archival instead of archiving changes individually?

You should use batch archival when you need to consolidate several parallel changes into a single archived record for project hygiene, reducing the manual overhead of processing them one by one.

What happens to conflicting deltas when archiving multiple changes simultaneously?

When archiving multiple changes simultaneously, conflicting deltas are resolved by inspecting the actual codebase implementation, ensuring the resulting archive accurately reflects the true project state.