openspec-bulk-archive-change

Archive multiple completed changes and resolve spec conflicts via codebase inspection.

Updated Mar 8, 2026

Search Tags:#codebase analysis #archive #conflict resolution #openspec #changes #batch operation

Ready to run

npx skills add https://github.com/deicer/codex-lb --skill openspec-bulk-archive-change-deicer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/deicer/codex-lb/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/deicer/codex-lb --skill openspec-bulk-archive-change-deicer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes by intelligently handling potential spec conflicts and ensuring a clean, organized workflow.

Core Features & Use Cases

Batch Archiving: Archive several completed changes in a single operation.
Conflict Resolution: Automatically detects and resolves conflicts when multiple changes affect the same capability specs by checking codebase implementation.
Status Summarization: Provides a clear overview of each change's status, including artifacts, tasks, and spec conflicts.
Use Case: When you have finished several parallel features and need to archive them, this skill helps you do so without manual conflict checking and resolution.

Quick Start

Use the openspec-bulk-archive-change skill to archive all completed changes.

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 feature changes at once without spec conflicts?▼

You can batch archive multiple completed development changes in a single operation. The process automatically resolves spec conflicts by examining codebase implementations, ensuring a clean workflow without manual conflict checking.

How does batch archiving resolve conflicts when changes affect the same capability specs?▼

Batch archiving resolves spec conflicts by analyzing codebase implementations directly. When multiple completed changes target the same specs, the system checks the actual implementation to determine the correct resolution.

What's the best way to archive several parallel features after they are finished?▼

Archiving several parallel features is best handled through batch operations that summarize artifact status, task completion, and delta spec analysis. This approach provides detailed outcome reporting after user confirmation.

Do I need to manually check task completion and artifact status before archiving changes?▼

No manual checking is needed. The bulk archive operation automatically summarizes each change's status, including artifact completion and task verification, before proceeding with the archiving process.

What happens if multiple changes modify the same specs during batch archiving?▼

When multiple changes modify the same specs, the bulk archive operation detects the conflict and intelligently resolves it by examining the codebase implementation to ensure accurate delta spec analysis.

Can I review the outcome after archiving multiple development changes in a batch?▼

Yes, batch archiving provides detailed outcome reporting after the operation completes. This includes status summaries of artifacts, tasks, and spec conflicts for all selected changes requiring user confirmation.