openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: farmountain

Archive multiple completed OpenSpec changes while preserving metadata.

Updated Aug 23, 2026

Search Tags:#codebase #CLI #conflict-resolution #openspec #changes #change-management #bulk-archive

Ready to run

npx skills add https://github.com/farmountain/end2end_full_vscode_copilot_learning_program --skill openspec-bulk-archive-change-farmountain

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/farmountain/end2end_full_vscode_copilot_learning_program/tree/main/.github/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/farmountain/end2end_full_vscode_copilot_learning_program --skill openspec-bulk-archive-change-farmountain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives multiple completed OpenSpec changes in a single operation, reducing clutter and preserving history.

Core Features & Use Cases

Batch archive selected changes with conflict-aware handling, keeping the codebase consistent.
Analyze artifacts, tasks, and delta specs to detect conflicts automatically where possible.
Preserve legacy change metadata and ensure archived changes remain traceable.

Quick Start

Use the openspec-bulk-archive-change skill to batch archive completed changes. The process guides you through selecting changes, validating statuses, resolving conflicts, and archiving to an archival folder.

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 changes in OpenSpec at once?▼

Bulk archiving in OpenSpec lets you move multiple completed changes to an archival folder in a single operation. The skill analyzes each change's status, detects conflicts in delta specs, and preserves metadata so archived changes remain traceable and your codebase stays consistent.

Can I detect conflicts before archiving changes with OpenSpec?▼

Yes. The bulk archive process inspects delta specs and artifact status automatically to identify conflicts before archiving. This conflict-aware handling ensures you resolve issues before moving changes, preventing codebase inconsistencies.

What happens to change metadata when I archive with OpenSpec?▼

Legacy change metadata is preserved during archiving, keeping archived changes fully traceable and queryable. The skill moves completed changes while maintaining all historical context and documentation.

How do I validate that changes are ready before bulk archiving?▼

The skill guides you through selecting changes and validates their status using the OpenSpec CLI. It confirms readiness and gathers artifact data before proceeding to archive, so only completed changes move to the archival folder.

Does bulk archiving work with delta specs and artifact conflicts?▼

Yes. The process analyzes active changes, inspects delta specs, and gathers artifact status to detect conflicts automatically. You can resolve conflicts during the guided workflow before completing the bulk archive operation.