openspec-bulk-archive-change

Batch-archive multiple completed Openspec changes with conflict detection.

26|1|Updated May 2, 2022
One-click install
npx skills add https://github.com/anssip/passlane --skill openspec-bulk-archive-change-anssip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/anssip/passlane/tree/main/.pi/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/anssip/passlane --skill openspec-bulk-archive-change-anssip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving multiple completed Openspec changes at once to simplify change management and avoid manual repetition.

Core Features & Use Cases

  • Batch-archive multiple changes in a single operation.
  • Detect and resolve spec conflicts by inspecting the codebase.
  • Preserve Openspec metadata and archive changes under a date-stamped path.

Quick Start

Select active changes and confirm to archive them to archive/YYYY-MM-DD-<name>.

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 archive multiple completed changes at once?

Batch-archiving changes requires the openspec CLI to identify active changes and perform conflict-aware archival. It prompts for selection and moves items to a date-stamped directory.

What does conflict-aware archival mean for codebase changes?

Conflict-aware archival inspects the codebase to detect and resolve spec conflicts before moving changes to the archive, preventing data loss during batch operations.

Do I need the openspec CLI to batch-archive changes?

Yes, the openspec CLI is required to identify active changes, prompt for selection, and perform the batch archival of completed changes.

Can I preserve Openspec metadata when archiving changes?

Yes, the batch archival process supports optional preservation of the .openspec.yaml file to keep Openspec metadata intact within the date-stamped archival directory.

How are archived changes organized in the directory structure?

Changes are organized under a date-stamped path formatted as archive/YYYY-MM-DD-<name>, ensuring chronological tracking of batch-archived changes.