skills.rest
ondata
ondataOFFICIAL
Explore all skills by this author →
Website𝕏@ondataitGitHub

openspec-bulk-archive-change

Batch-archive multiple OpenSpec changes with conflict resolution and dated paths.

9|16|Updated Oct 16, 2018
Search Tags:#automation#codebase#archive#conflict-resolution#batch#openspec#changes
One-click install
npx skills add https://github.com/ondata/albopopTwoDotZero --skill openspec-bulk-archive-change-ondata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/ondata/albopopTwoDotZero/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/ondata/albopopTwoDotZero --skill openspec-bulk-archive-change-ondata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving multiple completed OpenSpec changes in a single operation to simplify release management and history cleanliness.

Core Features & Use Cases

  • Batch-archive changes with conflict detection and resolution potentials.
  • Preserve important metadata and ensure .openspec.yaml is retained during moves.
  • Generate clear status reports and allow a single user-confirmed bulk operation.

Quick Start

Initiate a bulk archive for all active OpenSpec changes and follow the prompts to select changes, resolve conflicts, and archive them.

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 involves scanning active changes, resolving conflicts by inspecting delta specs against the codebase, and moving them into a dated archive path in a single confirmed operation.

What is the best way to resolve conflicts when archiving OpenSpec changes?▼

Resolving conflicts during OpenSpec archiving requires inspecting delta specs against the codebase to detect discrepancies, allowing you to address issues before moving changes safely into the archive path.

Does bulk archiving OpenSpec changes preserve my configuration file?▼

Bulk archiving preserves the original OpenSpec configuration, ensuring the .openspec.yaml file is retained during moves while maintaining metadata integrity for all archived changes.

Can I review the status of each change before completing a bulk archive?▼

You can review outcomes for each change because the bulk archiving process generates clear status reports, allowing a single user-confirmed operation after inspecting active changes and resolving conflicts.

How does batch archiving handle completed OpenSpec changes for release management?▼

Batch archiving handles completed OpenSpec changes by consolidating them into a dated archive path, simplifying release management and ensuring history cleanliness through a single bulk operation.

Related Skills

Explore More Software Engineering Skills→
wishx127wishx127

openspec-sync-specs

Merge openspec delta requirements into main capability specs in place.

Community
Intermediate
jeffbalagosajeffbalagosa
1

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes into a dated directory.

Community
Advanced
guillaumejayguillaumejay

openspec-bulk-archive-change

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

Community
Advanced
wishx127wishx127

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes after reviewing artifacts and resolving conflicts.

Community
Advanced