skills.rest
studyzy
studyzyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Archive multiple OpenSpec changes via the OpenSpec CLI with status validation.

10.2k|702|Updated Apr 12, 2012
Search Tags:#CLI automation#openspec#version-control#change-management#bulk-archive
One-click install
npx skills add https://github.com/studyzy/imewlconverter --skill openspec-bulk-archive-change-studyzy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/studyzy/imewlconverter/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/studyzy/imewlconverter --skill openspec-bulk-archive-change-studyzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the bulk archiving of completed changes in an OpenSpec project, simplifying archival workflows.

Core Features & Use Cases

  • Batch archiving: archive several completed changes in a single operation.
  • Status and conflict checks: verify artifact status, tasks, and incremental specs before archiving.
  • Audit-ready history: preserve archived changes under a date-stamped archive path for traceability.

Quick Start

Ensure the OpenSpec CLI is installed and accessible from your PATH. List active changes with openspec list --json and select the ones to archive. Confirm the operation to archive changes into openspec/changes/archive/YYYY-MM-DD-<change-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 archive multiple completed changes in an OpenSpec project at once?▼

You can archive multiple completed OpenSpec changes in one operation by running the OpenSpec CLI to validate statuses and conflicts before moving them into a date-stamped archive directory.

What does the OpenSpec bulk archive process check before moving changes?▼

Before archiving, the process validates artifact statuses, tasks, and optional incremental specs to ensure no unresolved conflicts exist across the selected changes.

Do I need the OpenSpec CLI installed to batch archive changes?▼

Yes, the OpenSpec CLI must be installed and accessible from your PATH to execute the deterministic bulk archival workflow for your changes.

Where are completed changes stored after a bulk archive operation?▼

Archived changes are preserved under openspec/changes/archive within a date-stamped directory formatted as YYYY-MM-DD-<change-name> to maintain audit-ready traceability.

Can I select specific completed changes to archive instead of all active ones?▼

Yes, you can list active changes using the CLI and select specific completed changes to batch archive, ensuring only validated items are moved into the date-stamped directory.

Related Skills

Explore More Software Engineering Skills→
LIDR-academyLIDR-academy
273

openspec-bulk-archive-change

Archives multiple completed changes in one operation via openspec CLI workflows.

Official
Advanced
DraculaboDraculabo
2.0k

openspec-archive-change

Archive completed OpenSpec changes with artifact checks and date-based naming.

Community
Advanced
yazelinyazelin
31

openspec-bulk-archive-change

Batch archive completed openspec changes and resolve spec conflicts.

Community
Advanced
inspedralbesinspedralbes

openspec-bulk-archive-change

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

Official
Advanced