skills.rest
hossam7amdy
hossam7amdyCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Moves verified inactive changes to date-stamped archive directories using the openspec CLI.

Updated Jan 23, 2026
Search Tags:#codebase#conflict-resolution#openspec#change-management#delta-spec#bulk-archive
One-click install
npx skills add https://github.com/hossam7amdy/easy-auth --skill openspec-bulk-archive-change-hossam7amdy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/hossam7amdy/easy-auth/tree/main/.agent/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/hossam7amdy/easy-auth --skill openspec-bulk-archive-change-hossam7amdy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation, streamlining maintenance workflows by moving archived changes out of active workspaces while preserving history and references.

Core Features & Use Cases

  • Conflict-aware archiving: Detects and resolves delta-spec conflicts before archiving to avoid overwriting important changes.
  • Automated batch processing: Archives multiple changes in one action, reducing manual overhead.
  • Audit-ready archiving: Preserves relevant metadata and creates date-stamped archive directories for traceability.

Quick Start

Start by selecting the active changes to archive, then confirm the batch operation to move them into an archive folder with a date prefix.

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 codebase without losing history?▼

Batch archiving completed changes moves them out of the active workspace into a date-stamped archival directory, preserving history and references. This streamlines maintenance workflows by processing multiple changes in a single operation.

How does conflict-aware archiving handle delta-spec conflicts?▼

Conflict-aware archiving validates spec changes against the codebase to determine what was actually implemented. It detects and resolves delta-spec conflicts before archiving to ensure important changes are not overwritten.

Do I need the openspec CLI to automate bulk archiving of active changes?▼

Yes, the openspec CLI is required to perform batch archiving. The operation uses the CLI to analyze active changes, validate them, and move them into the archive folder automatically.

What is the best way to archive multiple completed changes for audit traceability?▼

The best way for audit-ready archiving is to use automated batch processing that preserves relevant metadata and creates date-stamped archive directories. This ensures traceability for all archived changes.

Why should I validate spec changes against the codebase before archiving?▼

Validating spec changes against the codebase determines what was actually implemented before moving the files. This conflict resolution step prevents archiving incomplete or conflicting delta-specs.

Related Skills

Explore More Software Engineering Skills→
arestivoarestivo

openspec-bulk-archive-change

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

Community
Advanced
ruan-catruan-cat
4

openspec-archive-change

Archive completed changes into dated folders under openspec/changes/archive.

Community
Intermediate
zthxxxzthxxx

openspec-bulk-archive-change

Archive completed specification change directories after conflict analysis and codebase verification.

Community
Advanced
CatsofsufferingCatsofsuffering
5

openspec-bulk-archive-change

Batch archive completed OpenSpec changes with conflict-aware resolution.

Community
Advanced