openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict detection and metadata preservation.

149|22|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/luzhenqian/ai-coding-lab --skill openspec-bulk-archive-change-luzhenqian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/luzhenqian/ai-coding-lab/tree/main/agent/dev-bot/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/luzhenqian/ai-coding-lab --skill openspec-bulk-archive-change-luzhenqian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically batch-archive multiple completed OpenSpec changes in a single operation, reducing manual effort and ensuring consistency across change histories.

Core Features & Use Cases

  • Batch selection of active changes to archive.
  • Conflict detection and resolution by inspecting the codebase and change specs.
  • Optional spec synchronization to align delta specs with implemented code.
  • Archive with preservation of metadata and relevant configuration.
  • Comprehensive status reporting and audit trail.

Quick Start

Select the active changes to archive and follow the prompts to review conflicts, synchronize specs, and complete the bulk 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 batch-archive multiple completed OpenSpec changes at once?

Batch-archiving completed OpenSpec changes requires interactively selecting active changes, running conflict detection, and optionally synchronizing specifications before confirming the bulk archive operation.

What is the best way to handle conflict resolution during bulk change archival?

Conflict resolution during bulk archival involves inspecting the codebase and change specs to detect issues, resolving them interactively to ensure specification correctness before finalizing the archive.

Can I synchronize specifications with implemented code before archiving changes?

Yes, optional spec synchronization aligns delta specs with implemented code before archiving, ensuring archived specifications accurately match the codebase state before finalizing the bulk archive.

Does bulk archiving OpenSpec changes preserve metadata and audit trails?

Bulk archiving preserves metadata and relevant configuration while capturing detailed status reports, providing a comprehensive audit trail for all batch-archived changes within the OpenSpec workflow.

What happens if there are conflicts when archiving concurrent OpenSpec changes?

When conflicts occur during concurrent change archival, the system detects them by inspecting the codebase and prompts for interactive resolution, requesting confirmation before finalizing the bulk archive.

When should I avoid using bulk-archive for OpenSpec change management?

Avoid bulk-archiving OpenSpec changes when individual changes have unresolved conflicts or require pending specification synchronization, as batch operations assume prior conflict resolution for history consistency.