openspec-bulk-archive-change

Automate bulk archiving of specification changes with conflict detection and resolution.

Updated Jan 9, 2026

Search Tags:#automation #codebase #repository #spec #archive #conflict resolution

Ready to run

npx skills add https://github.com/Draft-Official/draft-web --skill openspec-bulk-archive-change-draft-official

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/Draft-Official/draft-web/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/Draft-Official/draft-web --skill openspec-bulk-archive-change-draft-official

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of batch-archiving multiple specification changes, reducing manual effort and ensuring consistency.

Core Features & Use Cases

Batch Processing: Select and archive multiple spec changes at once.
Conflict Detection & Resolution: Detects conflicts in delta specs and resolves them by analyzing codebase implementation evidence.
Use Case: Teams managing numerous spec updates can efficiently archive completed changes, resolve conflicts automatically, and maintain a clean project history.

Quick Start

Use the openspec-bulk-archive-change skill to archive selected spec changes after validating their implementation status and resolving conflicts automatically.

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 automate bulk archiving of spec changes in a large codebase?▼

Automate bulk archiving of spec changes by batch processing multiple updates, detecting delta spec conflicts, and applying resolution strategies based on codebase implementation evidence. This ensures safe, ordered application and maintains clean project history without manual effort.

How does intelligent conflict resolution work for delta specs?▼

Intelligent conflict resolution for delta specs works by analyzing codebase implementation evidence, checking delta spec differences, and applying changes in the correct order. It detects conflicts automatically during batch archiving and resolves them to ensure repository integrity and safety.

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

The best way to archive multiple specification changes at once is using batch processing that validates implementation status first. This approach automatically detects and resolves conflicts by analyzing code, ensuring consistency across large spec repositories while reducing manual overhead.

Can I use batch spec archiving for large repositories with numerous updates?▼

Yes, batch spec archiving is suitable for large repositories managing numerous spec updates. It efficiently handles multiple completed changes simultaneously, automatically resolving conflicts to maintain project hygiene and clean history across complex codebases.

When should I not use automated batch archiving for specification changes?▼

Avoid automated batch archiving when specification changes lack valid implementation evidence in the codebase. The conflict resolution mechanism relies on analyzing code and delta specs, so unvalidated or incomplete updates may compromise integrity and safety during the automated application process.