skills.rest
emergent-company
emergent-companyOFFICIAL
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Archive multiple completed changes with openspec CLI after validating status and resolving conflicts.

1|Updated Feb 6, 2026
Search Tags:#git#version control#workflow automation#archiving#change management#openspec
One-click install
npx skills add https://github.com/emergent-company/emergent.memory --skill openspec-bulk-archive-change-emergent-company
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/emergent-company/emergent.memory/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/emergent-company/emergent.memory --skill openspec-bulk-archive-change-emergent-company

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 spec conflicts and validating implementation status, preventing manual errors and saving significant time.

Core Features & Use Cases

  • Batch Archiving: Archive several completed changes in a single operation.
  • Conflict Resolution: Automatically detects and resolves conflicts between changes affecting the same capabilities by checking codebase implementations.
  • Status Validation: Verifies artifact status, task completion, and spec deltas before archiving.
  • Use Case: When you have finished work on several related features (e.g., different aspects of an authentication module), you can use this skill to archive them all efficiently, ensuring that spec conflicts are resolved correctly based on actual code.

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 git changes at once without manual errors?▼

You can archive multiple completed changes in a single batch operation to save time. This process validates artifact status, task completion, and delta specs before proceeding, preventing manual errors during change management.

What happens when multiple archived changes have spec conflicts affecting the same capabilities?▼

When spec conflicts occur during archiving, the system resolves them by checking the codebase for actual implementation status. It verifies the codebase to ensure that conflicting changes are accurately archived based on real implementation.

Do I need the openspec CLI to batch archive changes?▼

Yes, the openspec CLI is required for change management and status checks. Batch archiving depends on this CLI to validate artifact status, task completion, and spec deltas before proceeding with the operation.

How does status validation work before batch archiving completed changes?▼

Status validation verifies artifact status, task completion, and spec deltas before archiving proceeds. This ensures that only fully completed changes are batch archived, preventing incomplete work from entering the archive.

When should I use batch archiving instead of archiving changes individually?▼

Batch archiving is ideal when you have finished work on several related features, such as different aspects of an authentication module. It efficiently archives them all while intelligently handling spec conflicts based on actual code implementations.

Can I archive changes if some tasks within a change are not yet completed?▼

No, the skill validates task completion before proceeding with batch archiving. If tasks are not completed, the validation step will fail, preventing incomplete changes from being archived.

Related Skills

Explore More Software Engineering Skills→
ywh0606ywh0606

opsx-verify

Verify OpenSpec changes for completion and readiness before archiving.

Community
Intermediate
stevemac007stevemac007

openspec-archive-change

Archive completed changes in an experimental workflow using the openspec CLI.

Community
Advanced
AuroraWebSoftwareAuroraWebSoftware
41

openspec-bulk-archive-change

Archive multiple completed openspec changes with conflict resolution via codebase verification.

Official
Advanced
artagonartagon

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with conflict detection and spec syncing.

Official
Advanced