openspec-bulk-archive-change

Archives multiple completed development changes in a single batch operation.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/TbK0ng/silver-bullet-kernel --skill openspec-bulk-archive-change-tbk0ng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/TbK0ng/silver-bullet-kernel/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/TbK0ng/silver-bullet-kernel --skill openspec-bulk-archive-change-tbk0ng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving multiple completed development changes simultaneously, preventing manual errors and saving significant time.

Core Features & Use Cases

  • Batch Archiving: Archive several changes in a single operation.
  • Intelligent Conflict Resolution: Automatically handles spec conflicts by checking the codebase for actual implementation.
  • Use Case: When you have finished working on several parallel features (e.g., user authentication, API enhancements, UI updates), use this skill to archive them all efficiently.

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 git changes at once instead of one by one?

To archive multiple changes at once, you can batch archive several completed development changes in a single operation, preventing manual errors and saving significant time when managing parallel features.

What happens when there are spec conflicts during batch code archiving?

When spec conflicts occur during batch archiving, the skill intelligently resolves them by analyzing the codebase for actual implementations and user-selected changes to ensure accurate spec synchronization.

How do I review pending changes before executing a batch archive operation?

Before executing batch archiving, the skill provides a consolidated status table that lists all selected changes, allowing you to review and verify which completed development changes will be archived.

Can I synchronize specs automatically when archiving multiple version control changes?

Yes, automated spec synchronization is supported during batch archiving. The skill checks the codebase implementation to resolve conflicts and aligns specs automatically when processing multiple changes.

When should I use batch archiving for code management instead of individual archiving?

Batch archiving is ideal when you have finished working on several parallel features, such as user authentication and API enhancements, and need to archive all completed changes efficiently in one operation.

Does batch archiving require any specific dependencies to process multiple changes?

No specific dependencies are required to batch archive multiple changes. The skill operates independently using scripts and references to analyze the codebase and resolve spec conflicts internally.