openspec-bulk-archive-change

Archive completed specification change directories after conflict analysis and codebase verification.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/zthxxx/hams --skill openspec-bulk-archive-change-zthxxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/zthxxx/hams/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/zthxxx/hams --skill openspec-bulk-archive-change-zthxxx

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of archiving multiple completed specification changes efficiently and accurately.

Core Features & Use Cases

  • Batch archiving: Moves multiple completed change directories into archive folders with date stamps.
  • Conflict detection and resolution: Identifies spec conflicts across changes and assesses codebase evidence to determine appropriate resolutions.
  • Use Case: When managing dozens of spec modifications, this Skill enables users to bulk-archive changes while intelligently handling overlapping specifications and conflicts, saving time and reducing errors.

Quick Start

Use the openspec bulk archive change skill to select active changes, resolve any conflicts, and archive them in a single operation.

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 bulk archive completed specification changes in my codebase?

To bulk archive completed specification changes, you can automate the process by selecting active changes and moving them into archive folders with date stamps in a single operation. This ensures accurate archival while preserving code integrity.

What is the best way to resolve conflicts when archiving multiple spec modifications?

Resolving conflicts during spec archiving involves identifying overlapping specifications across changes and assessing codebase evidence to determine appropriate resolutions. This automated conflict resolution process ensures safe archival of change directories.

How does automated conflict resolution work for specification archiving?

Automated conflict resolution for specification archiving works by identifying spec conflicts across concurrent changes and evaluating implementation evidence in the codebase. This ensures accurate and safe archival of change directories without manual intervention.

Can I batch archive multiple completed change directories with date stamps?

Yes, you can batch archive multiple completed change directories. The process moves completed changes into archive folders and applies date stamps automatically, streamlining change management for teams handling multiple concurrent modifications.

When do I need automated conflict analysis for codebase spec changes?

You need automated conflict analysis for codebase spec changes when managing dozens of concurrent modifications. It intelligently handles overlapping specifications and conflicts, saving time and reducing errors during the bulk archiving process.