skills.rest
SAP
SAPOFFICIAL
Explore all skills by this author →
Website𝕏@SAPOpenSourceGitHub

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes into date-stamped folders after conflict resolution.

221|96|Updated May 18, 2022
Search Tags:#automation#workflow#codebase#openspec#changes#conflicts#bulk-archive
One-click install
npx skills add https://github.com/SAP/e-mobility-charging-stations-simulator --skill openspec-bulk-archive-change-sap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/SAP/e-mobility-charging-stations-simulator/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/SAP/e-mobility-charging-stations-simulator --skill openspec-bulk-archive-change-sap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes in bulk to save time and maintain an auditable history, reducing manual steps and human error.

Core Features & Use Cases

  • Batch-archive multiple completed changes in a single operation.
  • Validate status, tasks, and delta-specs before archiving to detect conflicts.
  • Resolve conflicts by inspecting the codebase and applying a deterministic archiving order.
  • Archive changes into date-stamped folders while preserving metadata (.openspec.yaml).

Quick Start

  1. List active changes with openspec list --json
  2. Select changes to archive
  3. Run the archive workflow to move changes to openspec/changes/archive/YYYY-MM-DD-<name>

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 completed OpenSpec changes in bulk?▼

To batch archive OpenSpec changes, select completed changes and run the archive workflow. This process validates statuses, tasks, and delta-spec conflicts before moving them into date-stamped archive folders.

How are delta-spec conflicts detected and resolved during bulk archiving?▼

Delta-spec conflicts are detected by checking tasks and delta-specs before archiving. Conflicts are resolved by inspecting the codebase and applying a deterministic archiving order to preserve history.

When should I use bulk archiving for my codebase changes?▼

You should use bulk archiving when you need to preserve history and streamline release workflows across multiple changes. It saves time and reduces manual steps and human error.

Does the OpenSpec archiving process preserve .openspec.yaml metadata?▼

Yes, the OpenSpec archiving process preserves .openspec.yaml metadata. Changes are archived into date-stamped folders to ensure traceability while maintaining original configuration files.

What is the best way to automate OpenSpec change archiving for a release workflow?▼

The best way to automate OpenSpec change archiving is using a bulk workflow that enforces deterministic ordering. It checks statuses and conflicts, then archives changes into traceable date-stamped folders.

Related Skills

Explore More Software Engineering Skills→
alexei-lexxalexei-lexx

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes while resolving delta-spec conflicts.

Community
Advanced
nuomi1nuomi1

openspec-archive-change

Archive completed openspec changes into date-stamped directories while preserving .openspec.yaml.

Community
Advanced
SiddharthChillaleSiddharthChillale

openspec-bulk-archive-change

Batch archive multiple completed openspec changes with validation and conflict detection.

Community
Advanced
inspedralbesinspedralbes

openspec-bulk-archive-change

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

Official
Advanced