openspec-bulk-archive-change

Archive multiple completed changes while resolving spec conflicts via codebase analysis.

9|1|Updated Jun 6, 2018
One-click install
npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-bulk-archive-change-edwardsnjd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/edwardsnjd/dot-files/tree/main/configuration/agents/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-bulk-archive-change-edwardsnjd

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 in a version control system, especially when dealing with parallel development efforts.

Core Features & Use Cases

  • Batch Archiving: Archive several completed changes simultaneously, reducing manual effort.
  • Intelligent Conflict Resolution: Automatically detects and resolves conflicts by analyzing codebase implementations before archiving.
  • Use Case: You have finished work on three related features (e.g., user authentication, profile updates, and notification settings). Instead of archiving them one by one, you can use this Skill to archive all three at once, with the Skill intelligently merging any overlapping spec changes.

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 changes in git at the same time?

To archive multiple completed changes simultaneously, use a batch archiving operation that lists active changes, validates task status, and executes the archive process in one consolidated action to reduce manual effort.

What is the best way to handle spec conflicts when archiving parallel development changes?

Handling spec conflicts during archiving is best done by an intelligent process that detects capability conflicts, searches the codebase implementations, and agentically resolves overlapping changes before executing the batch archive.

Can I archive several features at once if they have overlapping codebase implementations?

Yes, you can archive several features at once even with overlapping implementations. The process detects capability conflicts and examines the codebase to intelligently merge and resolve overlapping spec changes before archiving.

How does batch archiving validate if a change is ready to be archived?

Batch archiving validates readiness by listing active changes, prompting for selection, and checking artifact and task status. It displays a consolidated status table to confirm everything is valid before executing the archive operation.

When should I use batch archiving instead of archiving changes one by one?

You should use batch archiving instead of one-by-one archiving when you have finished work on multiple related features and need to streamline parallel development efforts by consolidating manual version control operations into a single action.