skills.rest
Catsofsuffering
CatsofsufferingCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Batch archive completed OpenSpec changes with conflict-aware resolution.

5|1|Updated Apr 8, 2026
Search Tags:#conflict-resolution#openspec#changes#audit-trail#bulk-archive#codebase-search
One-click install
npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-bulk-archive-change-catsofsuffering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/Catsofsuffering/CCGS/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-bulk-archive-change-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes in a single operation to reduce manual archival effort and keep histories tidy.

Core Features & Use Cases

  • Batch archive multiple changes efficiently, handling parallel work and conflicts with auditable results.
  • Preserve traceability through date-stamped archive paths and per-change metadata.
  • Use case: when several changes are finished, bulk-archive them to minimize manual steps and ensure consistent archival.

Quick Start

Run the bulk archive command to batch-archive selected 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 batch archive completed OpenSpec changes in one operation?▼

OpenSpec bulk archiving consolidates multiple completed changes into one safe operation, reducing manual effort. It handles parallel work and conflicts through an auditable process with date-stamped paths and per-change metadata reporting.

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

Conflict-aware resolution during bulk archival manages parallel changes through an auditable process. It enforces guardrails for per-change status reporting and safe archival paths, ensuring traceability when multiple changes finish simultaneously.

How does date-stamped archiving preserve traceability for codebase changes?▼

Date-stamped archiving preserves traceability by applying consistent timestamps to archive paths and retaining per-change metadata. This creates an auditable trail that tracks when each completed change was archived within the batch operation.

Can I archive multiple OpenSpec changes that were finished in parallel?▼

Yes, bulk archiving specifically supports changes finished in parallel by coordinating through an auditable archive process. It applies conflict-aware resolution and per-change status reporting to safely manage concurrent archival.

What are the limitations of bulk archiving OpenSpec changes?▼

Bulk archiving relies on guardrails for per-change status reporting and conflict-aware resolution, meaning incomplete changes or unresolved conflicts may block the batch. Ensure all selected changes are fully completed before initiating the archive operation.

Related Skills

Explore More Software Engineering Skills→
ywh0606ywh0606

opsx-bulk-archive

Archive multiple completed OpenSpec changes through a validation workflow.

Community
Intermediate
cookeyholdercookeyholder

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict resolution and date-stamped directories.

Community
Advanced
pacaplanpacaplan
30

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes and resolve spec conflicts via codebase analysis.

Community
Advanced
YangYuS8YangYuS8

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with status checks and conflict resolution.

Community
Advanced