openspec-bulk-archive-change

Batch-archive completed changes via the openspec CLI after validation checks.

1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/HerbertGao/qsl-cardhub --skill openspec-bulk-archive-change-herbertgao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/HerbertGao/qsl-cardhub/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/HerbertGao/qsl-cardhub --skill openspec-bulk-archive-change-herbertgao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables batch archival of multiple completed changes within a repository, preserving history and audit trails while minimizing manual steps.

Core Features & Use Cases

  • Batch archiving: archive several finished changes in a single operation.
  • Safe, user-driven workflow: always prompt for selection; never archive without explicit confirmation.
  • Pre-archival checks: verify change status, gather task completion data, and inspect incremental specs to identify potential conflicts.
  • Audit-ready output: preserve metadata and timestamps and retain archived records for traceability.

Quick Start

Run the openspec CLI to list active changes and initiate a batch archive, following prompts to select changes and confirm the 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 batch archive completed changes in a version-control repository?

Batch archiving completed changes uses the openspec CLI to archive multiple finished repository changes in a single operation while preserving historical metadata. It prompts for explicit selection and confirms the operation to ensure safe archival.

What is the best way to archive multiple finished changes without losing audit trails?

Archiving multiple finished changes via the openspec CLI preserves metadata and timestamps to retain archived records for traceability. It enforces pre-archival checks and timestamped archiving to maintain a complete audit trail across batch operations.

How does pre-archival conflict resolution work when bulk archiving changes?

Pre-archival conflict resolution inspects incremental specs and verifies change status to identify potential conflicts before batch archiving. It gathers task completion data to ensure only validated changes proceed to timestamped archival.

Can I archive several changes at once without manually confirming each one?

Batch archiving multiple changes requires explicit user selection and confirmation before proceeding, ensuring safe user-driven workflow. You select multiple finished changes in one prompt, but the CLI never archives without explicit confirmation.

When do I need to perform bulk archiving of repository changes?

Bulk archiving is needed when teams managing parallel changes require batch archival after validation and conflict-resolution checks. It minimizes manual steps by consolidating multiple completed change archival operations into a single batch process.

What happens to archived records and metadata after batch archiving changes?

Archived records retain metadata and timestamps after batch archiving, preserving historical data for audit-ready output and traceability. The openspec CLI ensures archived change records maintain their original metadata throughout the archival process.