skills.rest
durandom
durandomCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Archive completed openspec changes into a dated directory with metadata.

1|Updated Jan 21, 2026
Search Tags:#codebase#conflict-resolution#openspec#change-management#delta-specs#bulk-archive
One-click install
npx skills add https://github.com/durandom/layton --skill openspec-bulk-archive-change-durandom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/durandom/layton/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/durandom/layton --skill openspec-bulk-archive-change-durandom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed changes in bulk to reduce clutter and preserve history across parallel workstreams.

Core Features & Use Cases

  • Bulk detection of active changes and batch processing using openspec
  • Conflict-aware archiving with delta-spec analysis and codebase verification
  • Preserves metadata while moving changes into a dated archive directory for auditability

Quick Start

Run the bulk-archive command to batch-archive your 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 changes in a codebase with parallel workstreams?▼

Batch-archiving changes requires scanning active changes with openspec, evaluating statuses and delta specs, then moving changes into a date-stamped archive directory while preserving metadata for auditability.

What is conflict-aware archiving for delta specs?▼

Conflict-aware archiving analyzes delta specs and verifies the codebase before moving changes into an archive, ensuring parallel workstreams are processed safely without unresolved conflicts.

Does openspec bulk-archive preserve metadata when archiving changes?▼

Yes, bulk-archive preserves associated metadata while moving changes into a dated archive directory, ensuring organized history and auditability across completed workstreams.

How do I reduce clutter from completed changes across parallel workstreams?▼

Reduce clutter by running the bulk-archive command to batch-archive completed changes, scanning active changes with openspec and moving them into a dated archive directory for organized history.

What's the best way to archive several parallel changes in a project?▼

The best way is using openspec for bulk detection of active changes, performing conflict-aware batch processing with delta-spec analysis, then moving changes into a dated archive directory.

When should I not use bulk archiving for codebase change management?▼

Avoid bulk archiving when active changes have unresolved conflicts or incomplete statuses, as the process requires evaluating delta specs and verifying the codebase before moving changes into the archive.

Related Skills

Explore More Software Engineering Skills→
wzyxdwllwzyxdwll
14

openspec-bulk-archive-change

Batch-archive completed openspec changes while preserving specs and artifacts.

Community
Advanced
jerome-benoitjerome-benoit
57

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
daodaoedudaodaoedu

openspec-bulk-archive-change

Archive multiple OpenSpec changes with conflict detection and spec syncing.

Official
Advanced
sanfordzhangsanfordzhang
1

openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict-aware delta-spec handling.

Community
Advanced