skills.rest
GeTechG
GeTechGCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Batch-archive multiple OpenSpec changes with conflict detection and metadata preservation.

10|1|Updated Apr 10, 2019
Search Tags:#automation#conflict-resolution#openspec#changes#version-control#bulk-archive
One-click install
npx skills add https://github.com/GeTechG/LDYOM --skill openspec-bulk-archive-change-getechg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/GeTechG/LDYOM/tree/main/LDYOM2/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/GeTechG/LDYOM --skill openspec-bulk-archive-change-getechg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-archive multiple OpenSpec changes into an archive directory while preserving metadata and enabling conflict-aware reconciliation.

Core Features & Use Cases

  • Batch archival of multiple changes in a single operation.
  • Automatic conflict detection and resolution guidance based on delta specs and codebase evidence.
  • Preservation of change history and .openspec.yaml during archiving.
  • Use Case: Archive a set of resolved changes after a sprint to clean up active changes.

Quick Start

Review active changes, select the batch to archive, and confirm the operation to execute.

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

Batch-archiving multiple OpenSpec changes consolidates them into a centralized archive directory in a single operation, preserving metadata like .openspec.yaml and prompting for confirmation before execution.

How does conflict detection work when archiving parallel spec changes?▼

Conflict detection for parallel spec changes analyzes delta specs and codebase evidence to identify issues, providing resolution guidance and enforcing chronological spec application before safe archival.

What is the best way to clean up active OpenSpec changes after a sprint?▼

Cleaning up active OpenSpec changes after a sprint involves selecting resolved changes and batch-archiving them to preserve history and metadata while removing them from the active workspace.

Do I need to resolve spec conflicts before batch archiving?▼

You must resolve spec conflicts before batch archiving because the process applies conflict-aware reconciliation, prompting for user confirmation to ensure safe, chronological spec application.

Does batch archiving OpenSpec changes preserve change history and metadata?▼

Batch archiving OpenSpec changes preserves change history and .openspec.yaml metadata during the archival process, ensuring provenance and spec synchronization are maintained.

Related Skills

Explore More Software Engineering Skills→
rafazafarrafazafar

openspec-bulk-archive-change

Batch-archive multiple OpenSpec changes while resolving delta-spec conflicts.

Community
Advanced
unbound-forceunbound-force
3

openspec-archive-change

Archive completed OpenSpec changes with validation and provenance.

Official
Advanced
pacaplanpacaplan
30

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes and resolve spec conflicts via codebase analysis.

Community
Advanced
tatargabortatargabor
30

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes into a date-stamped directory.

Community
Advanced