skills.rest
dezkareid
dezkareidCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Batch-archive multiple OpenSpec changes with conflict-aware spec synchronization and reporting.

6|Updated Feb 13, 2021
Search Tags:#archive#conflict-resolution#openspec#changes#bulk-archive#spec-sync
One-click install
npx skills add https://github.com/dezkareid/dezkareid --skill openspec-bulk-archive-change-dezkareid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/dezkareid/dezkareid/tree/main/design-system/design-tokens/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/dezkareid/dezkareid --skill openspec-bulk-archive-change-dezkareid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed OpenSpec changes in a single operation, handling conflicts and preserving change history.

Core Features & Use Cases

  • Batch-archive changes with automatic spec synchronization where possible.
  • Detect and resolve delta-spec conflicts by inspecting codebase evidence.
  • Preserve configuration files and organize archived changes by date, making rollbacks and audits straightforward.

Quick Start

Select the changes you want to archive and confirm the bulk archive action to complete the operation.

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 archive multiple OpenSpec changes at once without causing spec conflicts?▼

Bulk archiving OpenSpec changes detects and resolves delta-spec conflicts by inspecting codebase evidence. It compares artifact statuses and tasks, builds a consolidated report, and preserves configuration files to ensure safe relocation.

What happens to configuration files when I bulk-archive OpenSpec changes?▼

When bulk-archiving OpenSpec changes, configuration files are preserved during relocation. The operation organizes archived changes by date, ensuring rollbacks and audits remain straightforward without losing essential project setup data.

How does batch archiving handle existing OpenSpec archives?▼

Batch archiving handles existing OpenSpec archives gracefully by preserving current configurations and recording outcomes for each change. It compares artifact statuses before relocating to prevent data loss during consolidation.

Can I resolve delta-spec conflicts automatically when archiving OpenSpec changes?▼

Delta-spec conflicts are resolved during OpenSpec archiving by inspecting codebase evidence. The process compares artifact statuses and tasks to synchronize specs automatically where possible before finalizing the relocation.

Why do I need a consolidated report before archiving OpenSpec changes?▼

A consolidated report verifies artifact statuses and tasks across selected items before archiving OpenSpec changes. It ensures safe batch relocation by confirming conflict resolution and configuration preservation.

Related Skills

Explore More Software Engineering Skills→
wzyxdwllwzyxdwll
14

openspec-bulk-archive-change

Batch-archive completed openspec changes while preserving specs and artifacts.

Community
Advanced
Charles5277Charles5277
45

openspec-bulk-archive-change

Archive multiple completed openspec changes and resolve delta-spec conflicts.

Community
Advanced
ConductionNLConductionNL

openspec-archive-change

Validate artifacts and tasks before archiving completed OpenSpec changes.

Official
Advanced
kunishkunish

openspec-bulk-archive-change

Batch-archive multiple OpenSpec changes into date-stamped directories with conflict resolution.

Community
Advanced