openspec-bulk-archive-change

Batch-archive multiple completed OpenSpec changes with conflict detection.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/nuomi1/vCalendar --skill openspec-bulk-archive-change-nuomi1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/nuomi1/vCalendar/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/nuomi1/vCalendar --skill openspec-bulk-archive-change-nuomi1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-archive completed OpenSpec changes to streamline workflows, reduce manual steps, and preserve a clean archival trail.

Core Features & Use Cases

  • Batch-select active changes from the codebase and archive them in a single operation
  • Detect and resolve delta-spec conflicts with automated guidance and auditable results
  • Preserve .openspec.yaml and organize archives under date-stamped directories for traceability

Quick Start

Use the openspec-bulk-archive-change skill to select active changes and batch-archive them according to conflict-resolution rules.

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 OpenSpec changes in a codebase?▼

Batch archiving OpenSpec changes targets active changes across your codebase, prompts for selection, and archives confirmed changes in a single operation. It preserves .openspec.yaml and organizes archives under date-stamped directories for traceability.

What happens when delta-spec conflicts occur during batch archival?▼

During batch archival, the skill detects delta-spec conflicts and provides automated guidance for deterministic conflict resolution. This ensures only confirmed changes are archived while maintaining an auditable directory structure.

Can I select specific active changes to archive instead of all of them?▼

Yes, the batch archival process prompts you to select which active changes from the codebase to archive. This allows you to confirm and archive only the selected changes in a single operation.

Does batch archiving OpenSpec changes require any dependencies?▼

Batch archiving OpenSpec changes requires no external dependencies. The skill operates independently to target active changes, detect delta-spec conflicts, and archive confirmed changes with an auditable directory structure.

Why should I use batch archival instead of archiving changes individually?▼

Batch archival streamlines workflows and reduces manual steps by consolidating multiple completed OpenSpec changes into a single operation. It provides post-operation reporting and preserves a clean archival trail with date-stamped directories.