skills.rest
nfelix25
nfelix25COMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Archive completed code changes and resolve spec conflicts via openspec CLI.

Updated Mar 3, 2026
Search Tags:#openspec#codebase management#change tracking#spec conflict resolution#code archiving
One-click install
npx skills add https://github.com/nfelix25/home-movies --skill openspec-bulk-archive-change-nfelix25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/nfelix25/home-movies/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/nfelix25/home-movies --skill openspec-bulk-archive-change-nfelix25

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages the archiving of multiple completed changes in a codebase, resolving spec conflicts and ensuring data integrity.

Core Features & Use Cases

  • Batch Archiving: Archive multiple completed changes simultaneously, simplifying the process.
  • Conflict Resolution: Intelligent handling of spec conflicts between changes.
  • Use Case: Ideal for teams that want to archive multiple code changes at once while maintaining code consistency.

Quick Start

Archive the completed changes for all active features.

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 code changes while resolving spec conflicts?▼

Batch archiving completed code changes while resolving spec conflicts involves analyzing your codebase implementation to detect and synchronize artifacts during migration. This ensures data integrity when finalizing multiple active features simultaneously.

How does spec conflict resolution work when archiving multiple codebase changes?▼

Spec conflict resolution during code archiving works by analyzing the codebase implementation to detect inconsistencies between completed changes. It automatically handles artifact migration and spec synchronization to maintain consistency across batch-archived features.

Do I need the openspec CLI to archive multiple completed code changes?▼

Yes, you need the openspec CLI to archive completed code changes. The CLI is required to perform change listing and execute status checks, which are necessary prerequisites for the batch archiving and conflict resolution process.

What is the best way to archive multiple active code changes at once?▼

The best way to archive multiple active code changes at once is using a batch archiving approach with intelligent spec conflict resolution. This allows teams to simultaneously migrate artifacts and synchronize specs rather than processing changes individually.

When should I avoid batch archiving for codebase changes?▼

You should avoid batch archiving codebase changes when active features have not reached completion status. Since the process relies on openspec CLI status checks, archiving incomplete changes will disrupt artifact migration, spec synchronization, and overall data integrity.

Related Skills

Explore More Software Engineering Skills→
Pony-UnicornPony-Unicorn
7

openspec-bulk-archive-change

Archive multiple completed openspec changes while resolving spec conflicts against codebase implementation.

Community
Advanced
nuitsjpnuitsjp
1

openspec-bulk-archive-change

Archive multiple completed changes while resolving spec conflicts via codebase analysis.

Community
Advanced
harqianharqian
1

openspec-bulk-archive-change

Archive multiple completed code changes using the openspec CLI.

Community
Advanced
lbrlabslbrlabs
9

openspec-bulk-archive-change

Archive multiple completed changes into date-stamped directories using the openspec CLI.

Official
Advanced