openspec-bulk-archive-change

Archive multiple completed openspec changes after verifying implementation and resolving conflicts.

Updated Feb 19, 2026

Search Tags:#automation #git #workflow #archiving #spec management #codebase verification

Ready to run

npx skills add https://github.com/B4san/Calix-Pass --skill openspec-bulk-archive-change-b4san

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes simultaneously, intelligently handling potential conflicts by verifying implementation in the codebase.

Core Features & Use Cases

Batch Archiving: Archive several completed changes in one operation.
Conflict Resolution: Automatically detects and resolves spec conflicts by checking code implementation.
Use Case: When you have finished work on several related features, use this skill to clean up your active changes by archiving them all at once, 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 one batch operation?▼

Batch archiving completed changes requires verifying implementation status and resolving spec conflicts simultaneously. This process synchronizes delta specs with codebase reality, ensuring accurate spec lifecycle management for all archived changes in a single operation.

What is spec management conflict resolution during codebase archiving?▼

Spec management conflict resolution during archiving detects inconsistencies by checking code implementation against delta specs. It uses agentic reasoning based on code analysis to automatically resolve conflicts, ensuring archived changes accurately reflect the codebase reality.

Do I need acfm CLI to automate spec lifecycle management?▼

Yes, acfm CLI is required for spec management to automate the archiving workflow. The CLI handles the operational spec synchronization, while agentic reasoning manages the conflict resolution by analyzing the codebase implementation status.

How to verify codebase implementation before archiving spec changes?▼

Verifying codebase implementation before archiving spec changes involves checking the actual code against delta specs to detect conflicts. This verification ensures accurate synchronization, preventing inconsistencies when multiple completed changes are archived simultaneously.

When should I avoid batch archiving multiple changes in my workflow?▼

You should avoid batch archiving multiple changes when the codebase implementation is incomplete or unverified. If delta specs have unresolved conflicts that cannot be automatically resolved through code analysis, archiving individually is safer to maintain spec consistency.