Verified:GitHub

openspec-bulk-archive-change

Archive completed changes in bulk and resolve spec conflicts via codebase analysis.

Updated Mar 8, 2026

Search Tags:#codebase analysis #change management #software development workflow #bulk archive #spec conflict resolution

Ready to run

npx skills add https://github.com/roger8b/slideflow --skill openspec-bulk-archive-change-roger8b

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/roger8b/slideflow/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/roger8b/slideflow --skill openspec-bulk-archive-change-roger8b

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of archiving multiple completed changes simultaneously, streamlining operations and reducing manual work.

Core Features & Use Cases

Bulk Archive: Archive several completed changes at once.
Spec Conflict Detection: Identifies and resolves conflicts between delta specs of overlapping changes.
Codebase Analysis: Checks codebase implementation to ensure correct specs are applied.
Use Case: Ideal for developers who need to archive a batch of changes, such as after a feature sprint, without manually reviewing each one.

Quick Start

Run the openspec-bulk-archive-change skill to archive all completed changes in the current project.

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 bulk after a sprint?▼

Bulk archiving completed changes is automated by running the skill to process multiple change archiving scenarios at once, reducing manual overhead. It checks the codebase and archives all completed changes simultaneously.

How does spec conflict resolution work when archiving overlapping changes?▼

Spec conflict resolution works by analyzing the codebase to detect and resolve conflicts between delta specs of overlapping changes during the bulk archiving process. This ensures correct specs are applied automatically.

What is the best way to automate change management for completed software features?▼

Automating change management is best handled by bulk archiving completed changes through codebase analysis. This detects spec conflicts and resolves them, streamlining software development workflow operations efficiently.

Can I archive several codebase changes at once without manually reviewing each one?▼

You can archive several changes at once without manual review by running the bulk archive skill. It analyzes the codebase implementation and resolves spec conflicts automatically for the entire batch.

Do I need any dependencies to run bulk archive operations for software development workflows?▼

No dependencies are required to run bulk archive operations. The skill operates independently using scripts to analyze the codebase and resolve spec conflicts for completed changes.

Why does bulk archiving fail when delta specs conflict between overlapping changes?▼

Bulk archiving encounters conflicts when delta specs of overlapping changes contradict each other. The skill addresses this by analyzing the codebase to resolve spec conflicts before completing the archive.