openspec-bulk-archive-change

Batch archive completed OpenSpec changes and resolve conflicts by inspecting the codebase.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/MeetTechnology/AutoHire --skill openspec-bulk-archive-change-meettechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/MeetTechnology/AutoHire/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/MeetTechnology/AutoHire --skill openspec-bulk-archive-change-meettechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive and manage multiple completed OpenSpec changes in a single operation, reducing clutter and preserving history.

Core Features & Use Cases

  • Batch archive completed changes with intelligent conflict handling by inspecting delta specs and the codebase.
  • Detect and resolve conflicts across changes to ensure consistent archiving results.
  • Preserve metadata and ensure archive directories retain traceability, including timestamps and original change context.

Quick Start

Choose the active OpenSpec changes and execute the bulk archive 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 archive multiple completed OpenSpec changes at once?

The bulk archive operation detects conflicts by inspecting delta specs and the codebase to ensure consistent archiving. It resolves conflicts across changes before archiving, preventing inconsistent results and preserving metadata like timestamps and original change context.

How does bulk archiving preserve OpenSpec change metadata?

Yes, you can use bulk archiving for multiple completed changes in a single operation. It is designed to reduce clutter by managing batch archiving intelligently, handling conflicts by inspecting delta specs and the codebase to ensure consistent results.

What is the best way to handle conflicts when archiving OpenSpec changes?

Before bulk archiving, you need active OpenSpec changes with completed artifacts, tasks, and delta specs. The bulk archive operation analyzes these elements to detect conflicts and requires a confirmation prompt before executing the batch process.

Do I need to confirm before archiving multiple OpenSpec changes?

After bulk archiving, you get a managed archive directory with reduced clutter and preserved history. The operation reports per-change outcomes, ensuring traceability with timestamps and original change context for all archived items.