openspec-bulk-archive-change

Archive completed codebase changes and resolve spec conflicts with the openspec CLI.

Updated Mar 14, 2026

Search Tags:#developer workflow #codebase management #spec conflict resolution #batch archiving #archive automation

Ready to run

npx skills add https://github.com/bharathwaaj/numlox --skill openspec-bulk-archive-change-bharathwaaj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/bharathwaaj/numlox/tree/main/.agent/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/bharathwaaj/numlox --skill openspec-bulk-archive-change-bharathwaaj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

Manages the archiving of multiple completed changes at once, with intelligent conflict resolution for spec changes.

Core Features & Use Cases

Batch Archiving: Archive several parallel changes simultaneously, reducing manual work.
Spec Conflict Resolution: Handles conflicts by checking the codebase for actual implementations, applying changes in chronological order if both implemented.
Use Case: For developers managing a complex codebase with many parallel changes, this Skill can automate the archiving process, ensuring all completed changes are safely archived and spec conflicts are addressed.

Quick Start

To archive completed changes, run the command 'archive-changes'. Select the changes to be archived from the list provided, confirm the operation, and the Skill will perform the archiving, including conflict resolution.

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 codebase changes without spec conflicts?▼

Batch archiving completed changes uses automated conflict resolution by checking the codebase for actual implementations. When conflicts occur, changes apply chronologically, ensuring parallel modifications are archived correctly without manual intervention.

What does spec conflict resolution do when archiving parallel changes?▼

Spec conflict resolution checks the codebase for actual implementations during archiving. If conflicting changes are both implemented, it applies them in chronological order to ensure the final archived state reflects the correct development sequence.

Do I need the openspec CLI to automate batch archiving of changes?▼

Yes, the openspec CLI is required as a dependency to automate batch archiving. The Skill operates within the development workflow context, using the CLI to check implementations and resolve spec conflicts during the archiving process.

How do I archive multiple completed changes using the archive-changes command?▼

Run the 'archive-changes' command, select the completed changes from the provided list, and confirm the operation. The Skill handles the archiving automatically, including checking implementations and resolving any spec conflicts.

What is the best way to handle spec conflicts when archiving multiple changes at once?▼

Automated batch archiving handles spec conflicts by checking the codebase for actual implementations and applying changes chronologically when both conflicting changes are implemented, ensuring correct archival order without manual conflict resolution.

Why does batch archiving apply changes in chronological order during conflicts?▼

When spec conflicts arise during batch archiving, chronological ordering ensures changes are applied based on their implementation timeline. The Skill checks the codebase for actual implementations and sequences conflicting changes to maintain historical accuracy.