openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: rozx

Batch-archive completed OpenSpec changes with conflict-aware plans and date-based folders.

25|4|Updated Nov 13, 2025

Search Tags:#workflow #codebase #archive #conflict-resolution #openspec #changes #bulk

Ready to run

npx skills add https://github.com/rozx/Tsukuyomi --skill openspec-bulk-archive-change-rozx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/rozx/Tsukuyomi/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/rozx/Tsukuyomi --skill openspec-bulk-archive-change-rozx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to archive multiple completed OpenSpec changes in a single operation, reducing manual overhead and keeping the change history organized.

Core Features & Use Cases

Batch selection of changes to archive, enabling efficient cleanup of completed workstreams.
Per-change validations including artifact status, task completion, and delta specs to ensure only ready changes are archived.
Conflict detection across selected changes by analyzing delta specs and potential cross-touching capabilities.
Automated conflict resolution by inspecting the codebase to determine actual implementation and applying the correct specs in the proper order.
Execution of archiving with a consistent directory structure under openspec/changes/archive/YYYY-MM-DD-<name>, preserving essential metadata.
Consolidated status reporting with a final summary of archived, skipped, and spec-sync outcomes.

Quick Start

Select the changes to archive, review the consolidated status, and confirm to execute the bulk 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 batch archive completed OpenSpec changes without causing spec conflicts?▼

Batch archiving OpenSpec changes detects spec conflicts across selected changes by analyzing delta specs and cross-touching capabilities, then resolves them by inspecting the codebase to determine actual implementation and applying specs in the correct order.

How does conflict resolution work when archiving multiple OpenSpec changes at once?▼

When archiving multiple OpenSpec changes, the system detects spec conflicts across delta specs and cross-touching capabilities, then inspects the codebase to determine actual implementation and applies the correct specs in the proper order.

What validations are required before an OpenSpec change can be archived?▼

Per-change validations check artifact status, task completion, and delta specs to ensure only ready changes are archived, while skipped items are reported in the final summary.

Where are archived OpenSpec changes stored and what metadata is preserved?▼

Archived changes are stored under openspec/changes/archive/YYYY-MM-DD-<name> with a consistent directory structure that preserves essential metadata for organized change history.

Can I archive OpenSpec changes that have incomplete tasks or missing artifacts?▼

Changes with incomplete tasks or missing artifacts are skipped during per-change validations and reported as skipped items in the final consolidated summary alongside archived changes and spec-sync outcomes.

What does the final summary include after a bulk OpenSpec change archive operation?▼

The final summary returns archived changes, skipped items, and spec-sync results, providing a consolidated status report of the bulk archive operation without requiring external prompts.