openspec-bulk-archive-change

Archive multiple completed changes while resolving spec conflicts against the codebase.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/charlestang/UnaEditor --skill openspec-bulk-archive-change-charlestang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/charlestang/UnaEditor/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/charlestang/UnaEditor --skill openspec-bulk-archive-change-charlestang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes 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 against the codebase.

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 implementation.
  • Use Case: When you have finished work on several related features (e.g., authentication, user profiles, permissions), you can use this skill to archive them all efficiently, ensuring spec consistency.

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 in a single operation?

To archive multiple completed git changes at once, you can batch archive them by validating implementations against the codebase and resolving spec conflicts chronologically before execution.

What is the best way to resolve spec conflicts when archiving several changes simultaneously?

Resolving spec conflicts during bulk archiving involves checking the codebase for actual implementation and applying changes chronologically if both conflicting specs are implemented.

How does batch validation work when archiving completed version control changes?

Batch validation for archiving changes works by checking the codebase for actual implementation, allowing user selection, and providing a consolidated status report before executing the archive operation.

Can I archive related features together if they affect the same capabilities in OpenSpec?

Yes, you can archive related features together by intelligently detecting and resolving spec conflicts between changes that affect the same capabilities through codebase validation.

When do I need to use bulk archiving for change management?

You need bulk archiving for change management when you have finished work on several related features, such as authentication or permissions, and want to archive them efficiently while ensuring spec consistency.