openspec-bulk-archive-change

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

5|Updated Sep 17, 2022
One-click install
npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-bulk-archive-change-kevinxo328
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/kevinxo328/mercari-scraper/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-bulk-archive-change-kevinxo328

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes efficiently, reducing manual multi-step archiving.

Core Features & Use Cases

  • Batch-archive active changes with conflict-aware handling by inspecting codebase
  • Resolve spec conflicts across changes using automated reasoning and chronological order
  • Maintain an auditable archive history under openspec/changes/archive

Quick Start

Select changes to archive, then confirm the batch operation to move archived changes into openspec/changes/archive dated folders.

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 the completed changes and confirming the batch operation, which moves them into dated folders under openspec/changes/archive automatically.

How are delta-spec conflicts resolved when archiving multiple changes together?

Delta-spec conflicts across selected changes are detected and resolved using automated reasoning and chronological order, ensuring that overlapping modifications are handled safely during the batch archive process.

Do I need the openspec CLI to archive changes in a batch?

Yes, batch archiving OpenSpec changes requires the openspec CLI and a repository layout containing an openspec/changes/archive directory to store the archived changes correctly.

What is the best way to archive completed codebase changes without manual steps?

Batch archiving completed codebase changes reduces manual multi-step archiving by applying conflict-aware handling to inspect the codebase and move changes into an auditable archive history.

Why does batch archiving changes inspect the codebase before moving files?

Inspecting the codebase during batch archiving enables conflict-aware handling, allowing the process to detect and resolve delta-spec conflicts across multiple selected changes before they are moved to the archive.