skills.rest
brainsnorkel
brainsnorkelCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Batch-archive multiple completed OpenSpec changes into a date-stamped directory.

Updated Feb 1, 2026
Search Tags:#automation#workflow#conflict-resolution#openspec#changes#batch-archive
One-click install
npx skills add https://github.com/brainsnorkel/channel-secrets --skill openspec-bulk-archive-change-brainsnorkel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/brainsnorkel/channel-secrets/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/brainsnorkel/channel-secrets --skill openspec-bulk-archive-change-brainsnorkel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving multiple completed OpenSpec changes is error-prone when done individually; this skill consolidates the process into a single, auditable operation.

Core Features & Use Cases

  • Batch archival of multiple active changes in one operation.
  • Automated conflict detection and resolution by inspecting delta specs and codebase evidence.
  • Maintains an auditable archive under openspec/changes/archive with a date-stamped directory.
  • Prompts user for changes to archive and requires explicit confirmation before proceeding.

Quick Start

Select the active changes you want archived and run the batch-archive operation.

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 OpenSpec changes in one operation?▼

Batch-archiving OpenSpec changes requires the openspec CLI to inspect active changes, validate artifact status, handle conflicts, and maintain an auditable archive under openspec/changes/archive.

How does conflict resolution work when archiving multiple OpenSpec changes?▼

Conflict resolution works by inspecting delta specs and codebase evidence to detect and resolve conflicts automatically. The batch-archive operation requires explicit user confirmation before proceeding with the archival.

Do I need the openspec CLI to archive changes in bulk?▼

Yes, the openspec CLI is required to inspect active changes, validate artifact status, handle conflicts, and maintain the auditable archive under openspec/changes/archive with a date-stamped directory.

What is the best way to archive multiple OpenSpec changes without errors?▼

The best way to archive multiple OpenSpec changes without errors is using a batch-archive workflow that consolidates the process into a single auditable operation, validating artifact status, resolving conflicts, and prompting for explicit confirmation.

Why does batch archiving OpenSpec changes require explicit confirmation?▼

Batch archiving requires explicit confirmation to prevent accidental data loss, ensuring all selected changes have valid artifact status, completed tasks, and resolved delta spec conflicts before moving them to the date-stamped archive directory.

Related Skills

Explore More Software Engineering Skills→
arestivoarestivo

openspec-bulk-archive-change

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

Community
Advanced
jaxxstormjaxxstorm
4

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes into date-stamped directories.

Community
Advanced
ywh0606ywh0606

opsx-verify

Verify OpenSpec changes for completion and readiness before archiving.

Community
Intermediate
LIDR-academyLIDR-academy
273

openspec-bulk-archive-change

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

Official
Advanced