skills.rest
wishx127
wishx127COMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes after reviewing artifacts and resolving conflicts.

Updated Jul 6, 2025
Search Tags:#archive#conflict resolution#change management#openspec#repository maintenance#spec sync
One-click install
npx skills add https://github.com/wishx127/mirror-server --skill openspec-bulk-archive-change-wishx127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/wishx127/mirror-server/tree/main/.codebuddy/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/wishx127/mirror-server --skill openspec-bulk-archive-change-wishx127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of reviewing, validating, and archiving several completed OpenSpec changes one by one.

Core Features & Use Cases

  • Batch change review: Collect active changes, let the user choose one or many, and summarize artifact and task status before proceeding.
  • Conflict-aware archiving: Detect overlapping capability specs, inspect implementation evidence in the codebase, and decide whether spec sync is needed.
  • Reliable repository cleanup: Move confirmed changes into a dated archive folder while preserving required metadata and reporting successes, skips, and failures.

Quick Start

Ask the skill to archive the selected completed OpenSpec changes and report any conflicts, warnings, or failures before moving them to the archive.

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 OpenSpec changes in a single batch?▼

To archive multiple OpenSpec changes in one batch, the Skill collects active change directories, summarizes artifact and task status, validates implementation evidence, and moves confirmed folders into a dated archive path.

What is the best way to handle conflict resolution when archiving OpenSpec repository changes?▼

Conflict resolution during OpenSpec archiving involves detecting overlapping capability specs, inspecting implementation evidence in the codebase, and determining whether spec sync is needed before safely moving change folders to the archive.

How do I validate implementation evidence before moving completed change folders to an archive?▼

Validating implementation evidence requires reviewing artifacts and tasks within OpenSpec change directories to confirm completion, checking for overlapping capabilities, and resolving any spec sync requirements before archiving.

Can I review and select specific OpenSpec changes for batch archiving instead of processing all active folders?▼

Yes, the batch review process collects active OpenSpec changes and lets you choose one or many specific folders to archive, summarizing their artifact and task statuses before proceeding with the cleanup.

What happens if there are failures or warnings during OpenSpec repository maintenance and archiving?▼

During OpenSpec archiving, the process reports successes, skips, and failures, highlighting any conflicts, warnings, or missing implementation evidence before moving confirmed change folders into the dated archive path.

Related Skills

Explore More Software Engineering Skills→
SiddharthChillaleSiddharthChillale

openspec-bulk-archive-change

Batch archive multiple completed openspec changes with validation and conflict detection.

Community
Advanced
tiagofurtiagofur

sdd-archive

Merge delta specs into main specs and archive completed change folders.

Community
Advanced
soyrochussoyrochus

openspec-bulk-archive-change

Archive multiple completed openspec changes in a single batch operation.

Community
Advanced
pabloimrik17pabloimrik17

openspec-bulk-archive-change

Archive multiple openspec changes with conflict detection and resolution.

Community
Advanced