skills.rest
AlexanderRadevich
AlexanderRadevichCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Archive multiple completed changes while resolving spec conflicts via codebase inspection.

Updated Aug 27, 2026
Search Tags:#git#version control#archive#openspec#spec management#changeset
One-click install
npx skills add https://github.com/AlexanderRadevich/SportowyHub_clientApp --skill openspec-bulk-archive-change-alexanderradevich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/AlexanderRadevich/SportowyHub_clientApp/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/AlexanderRadevich/SportowyHub_clientApp --skill openspec-bulk-archive-change-alexanderradevich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes simultaneously, preventing manual effort and potential errors when dealing with numerous updates.

Core Features & Use Cases

  • Batch Archiving: Archive several completed changes in a single operation.
  • Intelligent Conflict Resolution: Automatically detects and resolves spec conflicts by analyzing codebase implementations.
  • Use Case: When you have finished implementing several features that touch the same capability (e.g., authentication), this skill helps you archive them all at once, ensuring that only the implemented specifications are merged.

Quick Start

Use the openspec-bulk-archive-change skill to archive all completed 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 archive multiple completed spec changes at once in git?▼

Batch archiving allows you to archive multiple completed spec changes at once by selecting updates, validating artifact status and task completion, and confirming the batch operation before execution.

How does spec conflict resolution work when archiving multiple changesets?▼

Spec conflict resolution works by agentically investigating the codebase to check for actual implementation, ensuring that only the specifications you actually implemented are merged during the archive process.

What is the best way to manage spec conflicts when archiving changes that touch the same capability?▼

The best way to manage spec conflicts for changes touching the same capability is using intelligent conflict resolution, which analyzes the codebase to detect actual implementations and merges only those validated specs.

Do I need to validate task completion before archiving a changeset?▼

Yes, you need to validate task completion before archiving a changeset. The archive operation automatically checks artifact status, task completion, and delta specs to ensure only finished work is processed.

Can I select specific completed changes for batch archiving instead of all pending updates?▼

Yes, you can select specific completed changes for batch archiving. The process prompts you for selection, validates the chosen artifacts, resolves any conflicts agentically, and confirms the operation before executing the archive.

Related Skills

Explore More Software Engineering Skills→
arestivoarestivo

openspec-bulk-archive-change

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

Community
Advanced
mixomatmixomat

clean-gone-branches

Delete local git branches marked [gone] while skipping worktree branches.

Community
Intermediate
factorial-iofactorial-io
14

openspec-archive-change

Finalize and archive completed changes by verifying artifacts and tasks.

Official
Intermediate
inspedralbesinspedralbes

openspec-bulk-archive-change

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

Official
Advanced