skills.rest
SimplifyMyCloud
SimplifyMyCloudOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

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

Updated Jan 30, 2026
Search Tags:#codebase#archiving#conflict-resolution#openspec#change-management#bulk-archive#spec-sync
One-click install
npx skills add https://github.com/SimplifyMyCloud/gcp-bq-no-egress-dashboard-poc --skill openspec-bulk-archive-change-simplifymycloud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/SimplifyMyCloud/gcp-bq-no-egress-dashboard-poc/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/SimplifyMyCloud/gcp-bq-no-egress-dashboard-poc --skill openspec-bulk-archive-change-simplifymycloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregates and archives multiple completed OpenSpec changes in a single operation, reducing manual steps and maintaining a clean project history.

Core Features & Use Cases

  • Supports batch selection of active changes
  • Performs conflict-detection and optional automated resolution
  • Archives changes to a dated archive path while preserving configuration

Quick Start

Select the active changes you want to archive and confirm the batch operation to start the archival 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 multiple completed OpenSpec changes at once?▼

To batch-archive OpenSpec changes, select multiple active changes and confirm the batch operation to archive them safely in a single step while preserving project history and configuration files.

What does bulk archiving do to my codebase change history?▼

Bulk archiving moves completed changes to a dated archive path while preserving the full change history and ensuring repository integrity through delta-spec synchronization and automated conflict resolution.

Can I resolve conflicts automatically when archiving multiple OpenSpec changes?▼

Yes, batch-archiving multiple OpenSpec changes includes conflict-detection and optional automated resolution, ensuring delta-spec synchronization and repository integrity without manual intervention during the archival process.

When do I need to batch-archive changes instead of archiving them individually?▼

Batch-archiving changes is needed when multiple active changes exist and you want to reduce manual steps by archiving them together with automated status checks, conflict resolution, and delta-spec synchronization.

Does batch-archiving OpenSpec changes preserve my configuration files?▼

Yes, batch-archiving OpenSpec changes preserves configuration files by moving completed changes to a dated archive path while maintaining a clean project history and ensuring repository integrity.

What are the limitations of bulk archiving OpenSpec changes?▼

Bulk archiving OpenSpec changes requires multiple active changes to exist and may require user prompts for conflict resolution, meaning empty repositories or single-change setups cannot utilize the batch operation workflow.

Related Skills

Explore More Software Engineering Skills→
ywh0606ywh0606

opsx-bulk-archive

Archive multiple completed OpenSpec changes through a validation workflow.

Community
Intermediate
sanfordzhangsanfordzhang
1

openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict-aware delta-spec handling.

Community
Advanced
woutervanranstwoutervanranst
1

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes in a batch operation.

Community
Advanced
tungnguyen10tungnguyen10

openspec-bulk-archive-change

Batch archive completed openspec changes and resolve delta spec conflicts.

Community
Advanced