openspec-bulk-archive-change

Batch-archive completed changes and resolve spec conflicts in chronological order.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/Yager-42/-- --skill openspec-bulk-archive-change-yager-42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/Yager-42/--/tree/main/.codex/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/Yager-42/-- --skill openspec-bulk-archive-change-yager-42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving multiple completed changes manually is error-prone and time-consuming; this skill enables batch archiving with intelligent conflict handling by inspecting the codebase.

Core Features & Use Cases

  • Batch-archive multiple completed changes in a single operation
  • Detect and resolve spec conflicts by inspecting the repository before archiving
  • Preserve history and organize archived changes under a date-stamped directory

Quick Start

Select the active changes to archive and initiate the batch archive process.

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 changes in openspec without errors?

Batch archive multiple completed changes by reading active changes, prompting for selection, and verifying artifact status, tasks, and delta specs. It safely applies spec updates chronologically and moves changes to the archive directory with a current date.

What is the best way to resolve spec conflicts when archiving changes to the codebase?

Resolve spec conflicts during archiving by inspecting the codebase to detect discrepancies before applying updates. The batch archive process checks artifact status and delta specs to inform decisions and applies chronological spec updates to prevent conflicts.

How does openspec handle archiving completed changes that have overlapping delta specs?

Openspec handles overlapping delta specs by inspecting the codebase to detect conflicts and applying appropriate spec updates in chronological order. This ensures that batch archiving preserves history accurately without overwriting prior changes.

Can I archive several codebase changes at once if their artifact status is not verified?

Archiving changes with unverified artifact status is not recommended. The batch archive process specifically verifies artifact status, tasks, and delta specs before archiving to ensure completed changes are safely moved to the openspec archive directory.

Why does batch archiving changes manually take so long and how can I automate it?

Manual archiving is time-consuming because it requires checking each change individually. Automate it by selecting active changes to initiate a batch archive process that automatically verifies artifacts, resolves conflicts by inspecting the codebase, and applies chronological updates.