openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: max-loo

Batch-archive multiple completed OpenSpec changes with conflict detection.

2|Updated Oct 13, 2025

Search Tags:#codebase #archive #conflict-resolution #batch #openspec #change-management

Ready to run

npx skills add https://github.com/Max-Loo/multi-chat --skill openspec-bulk-archive-change-max-loo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/Max-Loo/multi-chat/tree/main/.trae/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/Max-Loo/multi-chat --skill openspec-bulk-archive-change-max-loo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-archiving multiple completed changes to simplify history while preserving traceability and avoiding drift.

Core Features & Use Cases

Batch-archive: archive multiple completed changes in a single operation with spec conflict resolution.
Conflict-aware: automatically detects spec conflicts across selected changes and resolves them using codebase evidence.
Safe archival: preserves .openspec.yaml and archives to date-stamped directories, with per-change status reporting and error handling.
Interactive prompts: requires user selection; never auto-archives without confirmation.

Quick Start

Run the skill to batch-archive all active changes after selecting 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 completed changes in OpenSpec without causing codebase drift?▼

Batch archive completed changes in OpenSpec by running a single operation that validates statuses, detects spec conflicts, and inspects the codebase to sync history while preserving traceability. It requires an OpenSpec CLI and prompts for user confirmation before proceeding.

What happens when archiving multiple OpenSpec changes causes spec conflicts?▼

When spec conflicts occur during OpenSpec archival, the process automatically detects them across selected changes and uses codebase evidence to prompt for user selection, ensuring conflicts are resolved safely before any history is simplified.

Does OpenSpec batch archival preserve configuration files like .openspec.yaml?▼

Yes, OpenSpec batch archival safely preserves your .openspec.yaml configuration files. It manages archival directories with date stamps and generates a consolidated status report with per-change error handling to ensure no configuration data is lost.

Can I automate OpenSpec change archival without manual confirmation?▼

No, you cannot automate OpenSpec change archival without manual confirmation. The interactive prompt requires user selection for conflict resolution and never auto-archives changes without explicit confirmation, prioritizing safe archival and traceability.

What's the best way to simplify OpenSpec history while maintaining traceability?▼

The best way to simplify OpenSpec history while maintaining traceability is batch archiving. It consolidates multiple completed changes into date-stamped directories, inspects the codebase to decide what to sync, and generates a status report for per-change tracking.