openspec-bulk-archive-change

Batch-archive OpenSpec changes with conflict detection and metadata preservation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-archive completed changes to streamline project hygiene by removing clutter from active changes.

Core Features & Use Cases

  • Active-change discovery: Detects all active changes with openspec list --json.
  • Safe batch selection: Prompts user for multi-select including "All changes" and prevents auto-selection.
  • Conflict-aware archiving: Validates artifacts, tasks, and delta specs, resolves conflicts by codebase analysis, and archives with historical metadata.

Quick Start

Use the bulk archive to batch archive all active changes in your OpenSpec workspace.

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 to clean up active project clutter?

To batch archive completed changes in OpenSpec, use this Skill to discover active changes, validate artifacts and tasks, resolve delta spec conflicts, and move items under openspec/changes/archive/YYYY-MM-DD-<name> while preserving .openspec.yaml.

What is the safest way to archive multiple parallel changes without losing metadata?

The safest way to archive multiple parallel changes is using a user-confirmed workflow that validates artifact statuses, inspects specs, resolves conflicts via codebase analysis, and preserves historical metadata and .openspec.yaml files during the move.

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

Conflict resolution during OpenSpec archiving works by inspecting delta specs and analyzing the codebase to detect and resolve conflicts before moving changes to the archive directory with preserved metadata.

Can I select all active changes at once for archiving, or do I need to confirm each one?

You can select all active changes at once via a multi-select prompt, but the workflow prevents auto-selection by requiring user confirmation before batch archiving to ensure safety.

Does batch archiving OpenSpec changes require any specific dependencies or components?

Batch archiving OpenSpec changes requires no external dependencies or components; it relies solely on the openspec list --json command and codebase analysis to execute the guided workflow.

Why should I archive completed OpenSpec changes instead of leaving them active?

Archiving completed OpenSpec changes streamlines project hygiene by removing clutter from active changes, making it easier to track ongoing work while preserving completed historical metadata and specs.