skills.rest
Rushtu99
Rushtu99COMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Batch-archive openspec changes and resolve delta-spec conflicts via the CLI.

Updated Mar 30, 2026
Search Tags:#archive#openspec#changes#batch-operations#conflicts#codebase-analysis#delta-specs
One-click install
npx skills add https://github.com/Rushtu99/Codex-ReVamped --skill openspec-bulk-archive-change-rushtu99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/Rushtu99/Codex-ReVamped/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/Rushtu99/Codex-ReVamped --skill openspec-bulk-archive-change-rushtu99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation to simplify change management, improve traceability, and reduce manual overhead.

Core Features & Use Cases

  • Batch-archive active changes by presenting a multi-select prompt and enforcing a single confirmation.
  • Detect and resolve delta-spec conflicts by analyzing the codebase, syncing only implemented specs, and archiving changes atomically.
  • Archive completed changes into an organized archive path (archive/YYYY-MM-DD-<name>) while preserving essential metadata and files like .openspec.yaml.

Quick Start

Use the skill to batch-archive your active changes, resolve conflicts automatically, and save archived changes under archive/YYYY-MM-DD-<name>.

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

To batch-archive openspec changes, the skill uses a multi-select prompt to select completed changes, analyzes delta-spec conflicts, inspects the codebase, and archives them atomically after final confirmation.

What are delta-spec conflicts and how are they resolved during archiving?▼

Delta-spec conflicts are overlapping specification changes across selected openspec changes. The skill resolves them by inspecting the codebase to sync only implemented specs before archiving the changes.

Do I need the openspec CLI to archive completed changes?▼

Yes, the openspec CLI is required to batch-archive changes. The skill relies on the CLI to analyze active changes, detect conflicts, and sync specifications before moving them to the archive path.

Where are archived openspec changes stored and what metadata is preserved?▼

Archived openspec changes are stored in an organized archive path formatted as archive/YYYY-MM-DD-<name>. This process preserves essential metadata and files like .openspec.yaml.

What happens if a conflict is detected across multiple selected changes?▼

If a conflict is detected, the skill inspects the codebase to sync only the implemented specs. It records per-change outcomes and requires a final confirmation before archiving the changes.

Related Skills

Explore More Software Engineering Skills→
guillaumejayguillaumejay

openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict resolution based on codebase evidence.

Community
Advanced
yazelinyazelin
31

openspec-bulk-archive-change

Batch archive completed openspec changes and resolve spec conflicts.

Community
Advanced
deicerdeicer

openspec-bulk-archive-change

Archive multiple completed changes and resolve spec conflicts via codebase inspection.

Community
Advanced
AkaraChenAkaraChen
25

openspec-bulk-archive-change

Batch-archive completed changes by validating active changes and resolving spec conflicts.

Community
Advanced