openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict resolution and configuration preservation.

5|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/agentxm/axm --skill openspec-bulk-archive-change-agentxm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/agentxm/axm/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/agentxm/axm --skill openspec-bulk-archive-change-agentxm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed OpenSpec changes one by one is tedious and error-prone; this Skill enables bulk archiving with safety checks and history preservation.

Core Features & Use Cases

  • Batch-archive multiple changes in a single operation.
  • Detect and resolve spec conflicts by inspecting the codebase to determine implementations.
  • Preserve configuration files (e.g., .openspec.yaml) during archiving and maintain an audit trail.

Quick Start

Select the changes you want to archive when prompted, then confirm to perform the batch archive.

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 OpenSpec changes at once?

To bulk-archive OpenSpec changes, select the completed changes from the prompt and confirm the operation. The Skill batch-archives them into a centralized archive while resolving spec conflicts and preserving your configuration files.

What happens when there are spec conflicts during codebase archiving?

When spec conflicts occur during archiving, the Skill resolves them by inspecting the codebase to determine the actual implementations. This ensures deterministic behavior and prevents incorrect archiving of conflicting change records.

Can I preserve .openspec.yaml configuration when archiving changes in bulk?

Yes, .openspec.yaml configuration files are preserved during the bulk archiving process. The Skill maintains your configuration and audit trail while moving completed OpenSpec changes to the centralized archive.

Does the batch archive process check for active changes before moving them?

Yes, the batch archive process checks for active changes before proceeding. It prompts for confirmation and enforces safety checks to ensure only completed OpenSpec changes are archived in the bulk operation.

Why should I use bulk archiving instead of archiving OpenSpec changes one by one?

Archiving OpenSpec changes one by one is tedious and error-prone. Bulk archiving enables you to batch multiple changes in a single operation with deterministic conflict resolution and history preservation, reducing manual overhead.