skills.rest
AGIBuild
AGIBuildCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

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

10|Updated Jan 28, 2026
Search Tags:#git#version control#archive#conflict resolution#spec management#changeset
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill openspec-bulk-archive-change-agibuild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill openspec-bulk-archive-change-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes simultaneously, intelligently handling potential spec conflicts by verifying implementation in the codebase.

Core Features & Use Cases

  • Batch Archiving: Archive several changes in a single operation, ideal for parallel development streams.
  • Intelligent Conflict Resolution: Automatically detects and resolves conflicts in specification deltas by checking actual code implementation.
  • Use Case: When you have finished work on several related features, use this skill to archive them efficiently, ensuring that spec changes are correctly merged or prioritized based on their real-world implementation.

Quick Start

Use the openspec-bulk-archive-change skill to archive all selected 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 changes at once instead of one by one?▼

Batch archiving completed changes allows you to process numerous parallel development streams in a single operation, automatically verifying codebase implementation to intelligently resolve specification conflicts and merge deltas.

How does conflict resolution work when merging spec changes from parallel branches?▼

Intelligent conflict resolution automatically detects conflicting specification deltas during batch archival and resolves them by checking actual codebase implementation, prioritizing specs based on real-world code.

Do I need the openspec CLI to manage batch changeset archival?▼

Yes, the openspec CLI is required to manage batch changeset archival, providing the necessary functionality for listing changes, checking completion status, and synchronizing specifications.

What is the best way to handle spec synchronization for numerous parallel changes?▼

The best way to handle spec synchronization for numerous parallel changes is through batch archival, which intelligently merges or prioritizes specification deltas based on their actual implementation in the codebase.

When should I avoid using batch archival for spec management?▼

You should avoid batch archival for spec management when your changes are not yet completed or when you need manual, granular control over individual specification conflicts rather than automated codebase-based resolution.

Related Skills

Explore More Software Engineering Skills→
pabloimrik17pabloimrik17

openspec-archive-change

Archive completed openspec changes after verifying artifacts and tasks.

Community
Advanced
cloudvoyantcloudvoyant

done

Complete and archive specification-driven development plans with Git commits and pull requests.

Official
Advanced
LuigiAPCPereiraLuigiAPCPereira

golang-dependency-management

Automate Go dependency vulnerability scanning and conflict resolution with govulncheck and directives.

Community
Advanced
MetaCubeXMetaCubeX
4.1k

openspec-bulk-archive-change

Archive multiple completed openspec changes with batch processing and delta spec synchronization.

Official
Advanced