openspec-bulk-archive-change

Archive multiple completed openspec changes with conflict resolution via codebase inspection.

6.2k|152|Updated Feb 7, 2024
One-click install
npx skills add https://github.com/PBH-BTN/PeerBanHelper --skill openspec-bulk-archive-change-pbh-btn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/PBH-BTN/PeerBanHelper/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/PBH-BTN/PeerBanHelper --skill openspec-bulk-archive-change-pbh-btn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables batch archiving of multiple completed changes, reducing manual overhead and ensuring consistency across parallel work items.

Core Features & Use Cases

  • Batch archiving: Archive several changes in a single operation.
  • Conflict handling: Detects delta-spec conflicts and uses codebase inspection to determine what is implemented.
  • Structured workflow: Guides the user through selection, validation, conflict resolution, archival, and reporting.

Quick Start

Use the openspec-bulk-archive-change skill to batch-archive several parallel changes.

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 completed changes in a codebase at once?

Batch archiving of multiple completed changes is done through a structured workflow that guides selection, validation, conflict resolution, and reporting to reduce manual overhead. It processes several parallel changes in a single operation.

What is the best way to resolve delta-spec conflicts when archiving parallel changes?

Resolving delta-spec conflicts during batch archival requires inspecting the codebase to verify what is actually implemented. The workflow validates status and determines implemented changes before proceeding with the archival operation.

How does batch archiving handle validation before processing completed changes?

Batch archiving validates the status of each completed change before processing. The structured workflow prompts for input, checks validation status, resolves any conflicts via codebase inspection, and reports the final archival outcome.

Can I archive several parallel work items without checking each one manually?

Archiving several parallel work items without manual checks is possible using a batch archival workflow. It automatically inspects the codebase to determine what is actually implemented and resolves delta-spec conflicts across all selected changes.

When do I need to use batch archival for completed changes?

Batch archival is needed when you have multiple completed changes from parallel work items that require consistent archival. It provides a structured workflow to handle selection, conflict resolution, and reporting in one operation.

Why does batch archiving inspect the codebase during conflict resolution?

Batch archiving inspects the codebase during conflict resolution to determine what is actually implemented. This ensures delta-spec conflicts are resolved accurately by verifying the true state of parallel changes before archival.