skills.rest
anaclumos
anaclumosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Batch-archive OpenSpec changes and resolve conflicts via codebase analysis.

Updated Aug 27, 2026
Search Tags:#automation#openspec#changes#conflicts#codebase-analysis#bulk-archive
One-click install
npx skills add https://github.com/anaclumos/verifidia --skill openspec-bulk-archive-change-anaclumos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/anaclumos/verifidia/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/anaclumos/verifidia --skill openspec-bulk-archive-change-anaclumos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving multiple completed OpenSpec changes in a single operation, reducing manual effort and preserving a clean change history.

Core Features & Use Cases

  • Batch selection: Pick multiple changes at once and decide whether to archive all or only ready ones.
  • Conflict-aware archiving: Detects delta-spec conflicts across changes and resolves them by inspecting the codebase.
  • Auditable archival: Preserves important metadata (.openspec.yaml) and records a dated archive path for each archived change.
  • Status reporting: Provides per-change status (archived, skipped, or failed) and a consolidated batch result.

Quick Start

Select the changes to archive and confirm to start the batch archiving process.

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 safely?▼

Yes, the batch archiving process detects delta-spec conflicts across selected OpenSpec changes and resolves them by inspecting the codebase for implementation evidence before moving records to the archive location.

How does bulk archiving handle spec conflicts across multiple changes?▼

The bulk archiving process detects delta-spec conflicts across selected changes and resolves them by analyzing the codebase for implementation evidence. It evaluates whether the conflicting specifications are actually implemented before proceeding with the archival.

Do I need the openspec CLI installed to bulk-archive changes?▼

Yes, the openspec CLI is required to execute the batch archiving process. The Skill uses the CLI to analyze the codebase, detect spec conflicts, and move completed change records to the designated archive location.

What happens to the .openspec.yaml file when archiving changes?▼

The original .openspec.yaml file is preserved during the batch archiving process. The operation maintains this metadata while moving completed change records to a dated archive path to ensure an auditable history.

Can I see the status of each change after a bulk archive operation?▼

The bulk archive operation provides per-change status reporting, outputting a consolidated batch result that shows whether each individual change was successfully archived, skipped, or failed during processing.

What are the limitations of batch-archiving OpenSpec changes?▼

A limitation of batch-archiving OpenSpec changes is that unresolved delta-spec conflicts without clear codebase implementation evidence can cause a change to fail or be skipped, requiring manual intervention before retrying the archival.

Related Skills

Explore More Software Engineering Skills→
guillaumejayguillaumejay

openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict resolution based on codebase evidence.

Community
Advanced
rock-hurock-hu

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict resolution and status reports.

Community
Intermediate
luifertorresluifertorres
1

openspec-bulk-archive-change

Batch-archive multiple completed openspec changes with automatic conflict resolution.

Community
Advanced
Rushtu99Rushtu99

openspec-bulk-archive-change

Batch-archive openspec changes and resolve delta-spec conflicts via the CLI.

Community
Advanced