openspec-bulk-archive-change

Batch-archive completed openspec changes while preserving .openspec.yaml metadata.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill batch-archives completed openspec changes, enabling consolidation of work and streamlined project hygiene without repeating manual steps.

Core Features & Use Cases

  • Bulk archiving: Archive multiple completed changes in a single operation.
  • Conflict-aware: Detects spec conflicts and resolves them by inspecting the codebase before archiving.
  • Auditable history: Preserves metadata and creates archived snapshots for traceability.

Quick Start

Use the openspec-bulk-archive-change skill to batch-archive all selected completed changes. First, list active changes, select those to archive, and confirm the operation. Then the tool will archive the chosen changes into an archive directory named with the current date.

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 openspec at once?

Batch-archive completed changes by listing active changes with openspec CLI, selecting those ready for consolidation, and confirming the operation. The skill archives selected changes into a dated archive directory while preserving .openspec.yaml and spec integrity.

Can I detect conflicts when archiving multiple openspec changes together?

Yes, the batch-archive process is conflict-aware. It inspects the codebase before archiving to detect spec conflicts, resolving them automatically so you consolidate work safely without manual conflict resolution steps.

What happens to my openspec metadata when I bulk-archive changes?

Bulk-archiving preserves .openspec.yaml and creates auditable archived snapshots with full metadata for traceability. Your project's spec integrity remains intact and all changes are recorded for historical reference.

When should I use batch-archiving instead of archiving changes individually?

Use batch-archiving for multi-change maintenance workflows where several changes are active simultaneously. It streamlines project hygiene by consolidating completed work in a single operation, eliminating repetitive manual steps.

Do I need the openspec CLI installed to run bulk-archive?

Yes, the openspec CLI is required. The skill interacts with openspec to list changes, validate statuses, detect conflicts, and perform the batch-archive operation in a single consolidated workflow.