openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: ishibata91

Batch-archive multiple OpenSpec changes with conflict-aware synchronization.

Updated Feb 3, 2026

Search Tags:#automation #archiving #conflict-resolution #openspec #change-management #batch-archive

Ready to run

npx skills add https://github.com/ishibata91/ai-translation-engine-2 --skill openspec-bulk-archive-change-ishibata91

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/ishibata91/ai-translation-engine-2/tree/main/.agent/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/ishibata91/ai-translation-engine-2 --skill openspec-bulk-archive-change-ishibata91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes at once, reducing manual archiving chores and ensuring consistent history.

Core Features & Use Cases

Batch-archive multiple active changes in a single operation with conflict-aware synchronization.
Validate and stage delta specs, perform codebase lookups to determine actual implementations.
Archive changes into date-stamped folders while preserving metadata and the .openspec.yaml.

Quick Start

Initiate a batch archive of all eligible OpenSpec changes in your workspace.

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 multiple OpenSpec changes in a single operation?▼

To batch-archive multiple OpenSpec changes, you can initiate a single operation that validates delta specs, stages files, and archives completed changes into date-stamped folders while preserving metadata and the .openspec.yaml configuration.

What is the best way to handle conflict resolution when archiving parallel OpenSpec changes?▼

Conflict resolution during OpenSpec archiving is handled through a guided workflow that performs codebase lookups to determine actual implementations, using code evidence to resolve synchronization conflicts across parallel changes.

When do I need to batch-archive OpenSpec changes instead of archiving them individually?▼

You need batch archiving when managing projects with parallel OpenSpec changes that require coordinated archiving, conflict-aware delta-spec synchronization, and consistent release history without manual individual archiving chores.

Does batch archiving OpenSpec changes preserve project metadata and configuration files?▼

Yes, batch archiving preserves project metadata and the .openspec.yaml configuration file by archiving changes into date-stamped folders while maintaining consistent history across all staged delta specs.

How does the OpenSpec batch archive workflow determine actual code implementations?▼

The OpenSpec batch archive workflow determines actual code implementations by performing codebase lookups during the validation and staging process, ensuring delta specs synchronize with the real code evidence before archiving.

Can I archive OpenSpec changes that have unresolved conflicts in my workspace?▼

Archiving OpenSpec changes with conflicts follows a guided workflow with prompts and conflict resolution based on code evidence, ensuring synchronization issues are addressed before changes are archived into date-stamped folders.