openspec-bulk-archive-change

Batch-archive multiple completed changes with conflict checks via the openspec CLI.

2|Updated Sep 23, 2025

Search Tags:#automation #codebase #openspec #changes #conflicts #bulk-archive

Ready to run

npx skills add https://github.com/tonysyu/gqlxp --skill openspec-bulk-archive-change-tonysyu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/tonysyu/gqlxp/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/tonysyu/gqlxp --skill openspec-bulk-archive-change-tonysyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation to simplify project housekeeping and rollback.

Core Features & Use Cases

Batch-archive parallel changes with conflict-aware handling by inspecting delta specs and codebase evidence.
Preserve history by moving archived changes under a dated directory while keeping the original configuration intact.
Safe, auditable workflow with explicit user prompts and detailed status reporting.

Quick Start

Select the changes to archive and confirm the bulk 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 bulk-archive multiple completed codebase changes at once?▼

To bulk-archive multiple completed codebase changes, you select the changes to archive and confirm the operation. The Skill performs status checks, prompts for selection, analyzes delta specs for conflicts, and moves changes into a dated folder while preserving configuration.

What happens when archiving parallel changes causes conflicts in my codebase?▼

When archiving parallel changes causes conflicts, the Skill analyzes delta specs and resolves conflicts by examining codebase evidence. This ensures coordinated releases or review cycles are handled safely without overwriting conflicting modifications.

Do I need the openspec CLI to archive multiple changes?▼

Yes, you need the openspec CLI installed to archive multiple changes. The Skill requires the openspec CLI to perform status checks, analyze delta specs, and execute the batch-archive operation into a dated directory.

Does archiving completed changes preserve the original openspec configuration?▼

Yes, archiving completed changes preserves the original openspec configuration. The Skill moves archived changes under a dated directory to maintain project history while keeping the original configuration completely intact.

What is the best way to streamline cleanup for coordinated release cycles?▼

The best way to streamline cleanup for coordinated release cycles is batch-archiving completed changes with conflict-aware handling. This workflow inspects delta specs, resolves conflicts by codebase evidence, and provides detailed status reporting for safe project organization.