skills.rest
llama-farm
llama-farmOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Batch-archive completed changes via the openspec CLI with conflict resolution.

2|Updated Feb 19, 2026
Search Tags:#codebase#archive#openspec#changes#conflicts#batch-archive
One-click install
npx skills add https://github.com/llama-farm/demofly-claude --skill openspec-bulk-archive-change-llama-farm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/llama-farm/demofly-claude/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/llama-farm/demofly-claude --skill openspec-bulk-archive-change-llama-farm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes at once, coordinating with the openspec CLI and handling conflicts to ensure clean archival.

Core Features & Use Cases

  • Bulk-archiving: batch archive of multiple completed changes in a single operation.
  • Conflict-aware: detects and resolves spec conflicts by inspecting delta specs and codebase.
  • Auditable archiving: preserves change history with date-stamped archive paths and preserves .openspec.yaml.

Quick Start

Follow the prompts to select changes and execute batch archival.

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 causing conflicts?▼

Batch-archiving completed changes is handled by coordinating the openspec CLI with conflict-resolution logic to inspect delta specs and the codebase, ensuring clean archival of parallel changes to date-stamped paths.

What happens when parallel changes have delta-spec conflicts during batch archival?▼

Delta-spec conflicts are detected by inspecting delta specs and the codebase to determine implemented changes, resolving conflicts before archiving to openspec/changes/archive with date-stamped paths.

Does batch archiving changes require the openspec CLI to validate task completion?▼

The openspec CLI is required to validate artifact and task completion before archiving, ensuring only fully completed changes are moved to the archive directory.

Can I use interactive prompts to select which completed changes to archive in bulk?▼

Interactive multi-select prompts are supported for choosing which completed changes to batch-archive, allowing you to coordinate multiple changes in a single operation.

How does openspec preserve change history when archiving multiple changes at once?▼

Auditable archiving preserves change history by moving changes to openspec/changes/archive with date-stamped paths while retaining the .openspec.yaml file for traceability.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

openspec-bulk-archive-change

Archive multiple OpenSpec changes with conflict detection and spec syncing.

Official
Advanced
nuomi1nuomi1

openspec-archive-change

Archive completed openspec changes into date-stamped directories while preserving .openspec.yaml.

Community
Advanced
SiddharthChillaleSiddharthChillale

openspec-bulk-archive-change

Batch archive multiple completed openspec changes with validation and conflict detection.

Community
Advanced
JanuaryLabsJanuaryLabs
4

openspec-bulk-archive-change

Archive multiple completed openspec changes with validation and conflict resolution.

Official
Advanced