skills.rest
zh-impact
zh-impactCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes while detecting and resolving spec conflicts.

Updated Aug 27, 2026
Search Tags:#automation#archive#openspec#change-management#bulk#codebase-analysis#spec-conflicts
One-click install
npx skills add https://github.com/zh-impact/fcollections --skill openspec-bulk-archive-change-zh-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/zh-impact/fcollections/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/zh-impact/fcollections --skill openspec-bulk-archive-change-zh-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation by coordinating batch archiving and conflict resolution to keep the codebase clean.

Core Features & Use Cases

  • Batch-archive multiple OpenSpec changes at once while detecting and resolving spec conflicts by inspecting the codebase.
  • Validate artifacts and task completion before archiving to ensure only fully implemented changes are archived.
  • Preserve existing .openspec.yaml during moves and provide a clear, auditable trail of archived items.

Quick Start

Select the changes to archive and confirm to execute the batch 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 multiple completed OpenSpec changes safely?▼

Batch archiving completed OpenSpec changes is handled by analyzing active changes, evaluating artifacts and delta specs, and resolving conflicts via codebase inspection before moving items into a dated folder.

How does conflict resolution work when archiving OpenSpec changes in bulk?▼

Conflict resolution during bulk archiving works by inspecting the codebase to detect spec conflicts across active changes, resolving them automatically before the archive operation executes to ensure codebase integrity.

Can I validate task completion before archiving OpenSpec changes?▼

Yes, the bulk archive operation validates artifacts and task completion before archiving to ensure only fully implemented OpenSpec changes are archived, preventing incomplete work from being moved.

Does archiving OpenSpec changes preserve the original configuration?▼

Archiving preserves the existing .openspec.yaml configuration during the move to a dated folder, maintaining original settings while providing a clear, auditable trail of archived items.

What is the best way to archive multiple OpenSpec changes at once?▼

The best way to archive multiple OpenSpec changes at once is executing a batch operation that coordinates archiving and conflict resolution, keeping the codebase clean by processing all selected items in a single pass.

What happens if spec conflicts are detected during a bulk OpenSpec archive?▼

When spec conflicts are detected during a bulk archive, the operation resolves them by inspecting the codebase before archiving, ensuring only clean, conflict-free changes are moved to the dated archive folder.

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
lz-freedomlz-freedom

openspec-archive-change

Archive validated openspec changes into dated archive folders with metadata.

Community
Advanced
cynkracynkra
1

openspec-bulk-archive-change

Archive multiple active OpenSpec changes after validating task completion and resolving delta-spec conflicts.

Official
Advanced
tungnguyen10tungnguyen10

openspec-bulk-archive-change

Batch archive completed openspec changes and resolve delta spec conflicts.

Community
Advanced