skills.rest
psacc
psaccCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Query openspec to select and archive completed changes with date-stamped folders.

1|Updated Feb 24, 2026
Search Tags:#automation#codebase#openspec#changes#conflicts#delta-specs#bulk-archive
One-click install
npx skills add https://github.com/psacc/omnisess --skill openspec-bulk-archive-change-psacc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/psacc/omnisess/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/psacc/omnisess --skill openspec-bulk-archive-change-psacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation, saving time and reducing manual overhead during batch maintenance.

Core Features & Use Cases

  • Batch-archive changes while preserving related metadata and ensuring safe relocation of change data.
  • Resolve conflicts automatically by aligning delta specs with implemented code, and provide a guided, auditable workflow for release readiness.
  • Use Case: Teams archiving a set of parallel changes after a release, with automated validation and optional confirmation prompts.

Quick Start

Execute the bulk archive command and confirm the changes to archive.

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

You can batch-archive multiple openspec changes by querying active changes, verifying their task completion, and safely relocating them to a date-stamped archive folder. The workflow validates artifact status and handles delta spec conflicts before finalizing the batch relocation.

What is the safest way to batch-archive delta specs after a release?▼

The safest way to batch-archive delta specs is using an automated workflow that aligns delta specs with implemented code, validates task completion status, and provides a guided confirmation prompt before relocating files to openspec/changes/archive with metadata preservation.

How are conflicts handled when archiving multiple openspec changes simultaneously?▼

Conflicts during openspec bulk archiving are handled per policy by automatically aligning delta specs with the implemented codebase before relocation. This validates artifact status and resolves discrepancies between change artifacts and actual implementation during the batch archive process.

Can I archive parallel openspec changes without losing metadata?▼

Yes, archiving parallel openspec changes preserves all related metadata by moving each change into a date-stamped folder within openspec/changes/archive. The bulk operation verifies artifact status and task completion beforehand to ensure safe metadata relocation.

When should I avoid bulk archiving changes in my codebase?▼

Avoid bulk archiving changes when active tasks are incomplete or artifact statuses cannot be verified beforehand. The process requires confirming task completion and resolving delta spec conflicts against the codebase to prevent misalignment or data loss during relocation.

Related Skills

Explore More Software Engineering Skills→
arestivoarestivo

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes while resolving delta-spec conflicts.

Community
Advanced
cookeyholdercookeyholder

openspec-bulk-archive-change

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

Community
Advanced
daodaoedudaodaoedu

openspec-bulk-archive-change

Archive multiple OpenSpec changes with conflict detection and spec syncing.

Official
Advanced
inspedralbesinspedralbes

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes and resolve delta-spec conflicts.

Official
Advanced