skills.rest
morganabel
morganabelCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Batch-archive completed changes and resolve spec conflicts via openspec CLI.

Updated Nov 15, 2025
Search Tags:#archive#batch processing#change management#spec conflict resolution#codebase integrity
One-click install
npx skills add https://github.com/morganabel/daily-workout --skill openspec-bulk-archive-change-morganabel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/morganabel/daily-workout/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/morganabel/daily-workout --skill openspec-bulk-archive-change-morganabel

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of archiving multiple completed changes at once, streamlining the process and avoiding manual errors.

Core Features & Use Cases

  • Batch-Archive Changes: Archive several parallel changes with a single operation, saving time and reducing the risk of mistakes.
  • Conflict Detection and Resolution: Intelligently handles spec conflicts by checking the codebase, ensuring data integrity.
  • Use Case: Ideal for managing multiple feature implementations or bug fixes, especially when working on large, complex projects.

Quick Start

Run the 'openspec-bulk-archive-change' skill to start the batch archive process.

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 changes in a software development project?▼

You can batch archive completed changes in a single operation to streamline project management and avoid manual errors. This process archives several parallel feature implementations or bug fixes at once while ensuring codebase integrity.

How does bulk archiving handle spec conflict resolution for implemented changes?▼

Spec conflict resolution during bulk archiving intelligently checks the codebase to ensure only implemented changes are archived. This mechanism verifies project data integrity by detecting and resolving specification conflicts across parallel changes before completing the archive operation.

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

Yes, you need the openspec CLI installed to operate the batch archiving process. This dependency is required to automate the bulk archiving of completed changes and handle spec conflicts for codebase integrity.

What is the best way to manage multiple parallel changes without risking codebase integrity?▼

The best way to manage multiple parallel changes is using batch archiving to process completed implementations in a single operation. This approach intelligently handles spec conflicts by checking the codebase, ensuring data integrity without manual errors.

When should I avoid batch archiving completed changes in my project?▼

You should avoid batch archiving when changes are not yet fully implemented or when unresolved spec conflicts exist. The process ensures data integrity by archiving only completed changes, so unverified or incomplete implementations should be handled individually.

Related Skills

Explore More Software Engineering Skills→
kunishkunish

openspec-verify-change

Verify changes against delta specifications and artifacts using the openspec CLI.

Community
Advanced
yazelinyazelin
31

openspec-bulk-archive-change

Batch archive completed openspec changes and resolve spec conflicts.

Community
Advanced
optionioptioni

openspec-bulk-archive-change

Batch archive completed codebase changes with openspec CLI conflict resolution.

Official
Intermediate
DanielShuguangDanielShuguang

openspec-bulk-archive-change

Archive multiple completed changes while resolving specification conflicts via code analysis.

Community
Advanced