openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict-aware delta-spec handling.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sanfordzhang/blockgame --skill openspec-bulk-archive-change-sanfordzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/sanfordzhang/blockgame/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/sanfordzhang/blockgame --skill openspec-bulk-archive-change-sanfordzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed openspec changes in a single operation to keep your workspace clean and organized.

Core Features & Use Cases

  • Batch-archive multiple changes in one go, with conflict-aware delta spec handling.
  • Preserve archived changes for auditing and traceability.
  • Use Case: When several changes are ready to be archived, this skill consolidates them while resolving any spec conflicts.

Quick Start

Archive all completed changes you want to retire by selecting from the active changes list.

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 to clean up the active workspace?

You can bulk-archive completed openspec changes by parsing the active changes list, evaluating task and artifact statuses, and executing a conflict-resolved archival operation to clean up your workspace.

What happens to delta specs when I batch-archive multiple changes at once?

When batch-archiving multiple changes, the skill performs conflict-aware delta-spec handling to resolve any spec conflicts, preserving archived changes for auditing and traceability.

When should I use batch-processing to archive codebase changes instead of archiving them individually?

You should use batch-processing for archiving codebase changes when several changes are ready for retirement simultaneously, requiring conflict-aware delta-spec handling and archived history retention.

Can I preserve archived openspec changes for auditing after batch-archiving?

Yes, batch-archiving completed openspec changes preserves archived changes for auditing and traceability while consolidating multiple changes and resolving any spec conflicts in one operation.

Why does conflict resolution matter when archiving multiple openspec changes together?

Conflict resolution matters during archival because the skill evaluates task and artifact statuses to perform a conflict-resolved archival operation, ensuring delta specs do not clash when multiple changes are consolidated.

Does batch-archiving changes require parsing all active changes in the workspace first?

Yes, the skill requires parsing active changes and evaluating task and artifact statuses before reading delta specs to perform the conflict-resolved batch archival operation.