skills.rest
inspedralbes
inspedralbesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes and resolve delta-spec conflicts.

Updated Apr 10, 2026
Search Tags:#automation#codebase#archive#batch#openspec#changes#conflicts
One-click install
npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill openspec-bulk-archive-change-inspedralbes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW/tree/main/prj-entrades-nou/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill openspec-bulk-archive-change-inspedralbes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automating the bulk archival of completed OpenSpec changes addresses the tedious manual task of archiving each change individually.

Core Features & Use Cases

  • Batch-archive multiple completed changes in a single operation to streamline release management.
  • Detect and resolve delta-spec conflicts across selected changes using codebase evidence to determine implemented specifications.
  • Preserve change history by moving archived changes under a dated archive path and ensuring static .openspec.yaml remains intact.

Quick Start

Select the active changes and confirm to archive them in a batch.

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 at once?▼

You can batch-archive multiple OpenSpec changes by selecting active changes and confirming the operation. This moves completed changes to a dated archive path in a single step while preserving history and static .openspec.yaml files.

How does bulk archiving handle delta-spec conflicts across parallel changes?▼

Bulk archiving detects delta-spec conflicts across selected changes automatically. It uses codebase evidence to determine implemented specifications and proposes automated resolutions before moving changes to the archive.

Can I archive OpenSpec changes in workflows with parallel branches?▼

Yes, you can archive changes in parallel workflows. The process detects artifact and delta-spec conflicts across selected changes and proposes resolutions based on codebase evidence, requiring a review step before archiving.

Do I need an active OpenSpec setup to archive changes in bulk?▼

Yes, an active OpenSpec setup is required. You also need a list of changes to archive and must complete a review and confirmation step before the changes are moved to the archive path.

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

The static .openspec.yaml file remains intact during the bulk archive process. The operation preserves change history by moving archived changes under a dated archive path without altering static configurations.

Related Skills

Explore More Software Engineering Skills→
DraculaboDraculabo
2.0k

openspec-bulk-archive-change

Batch-archive multiple completed OpenSpec changes with conflict detection and codebase validation.

Community
Advanced
081595081595

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with conflict resolution and spec syncing.

Community
Advanced
cynkracynkra
1

openspec-bulk-archive-change

Archive multiple active OpenSpec changes after validating task completion and resolving delta-spec conflicts.

Official
Advanced
CatsofsufferingCatsofsuffering
5

openspec-bulk-archive-change

Batch archive completed OpenSpec changes with conflict-aware resolution.

Community
Advanced