skills.rest
optioni
optioniOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Batch archive completed codebase changes with openspec CLI conflict resolution.

Updated Apr 13, 2026
Search Tags:#archiving#conflict resolution#codebase management#bulk processing#specification handling
One-click install
npx skills add https://github.com/optioni/dungeons-and-dragons --skill openspec-bulk-archive-change-optioni
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/optioni/dungeons-and-dragons/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/optioni/dungeons-and-dragons --skill openspec-bulk-archive-change-optioni

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages bulk archiving of completed changes, offering a streamlined approach for maintaining a clean and organized spec environment with intelligent conflict resolution.

Core Features & Use Cases

  • Bulk Archiving: Archive multiple completed changes simultaneously to maintain a tidy spec environment.
  • Conflict Resolution: Handles spec conflicts intelligently by checking the codebase, ensuring that only implemented changes are archived.
  • Use Case: When you have several parallel changes that have been completed, this skill allows you to archive them all at once, reducing manual steps and ensuring consistency.

Quick Start

To archive all completed changes, run the openspec-bulk-archive-change skill.

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

Bulk archiving handles spec conflicts by checking the codebase for implementation status before proceeding. If conflicts exist, it resolves them by applying change specifications in chronological order, ensuring only successfully implemented changes are archived.

Do I need the openspec CLI to manage bulk specification archiving?▼

You need the openspec CLI installed to manage codebase specifications for bulk archiving. The skill relies on the openspec dependency to execute batch operations and verify implementation status across your codebase.

What is the best way to handle specification conflicts when archiving changes?▼

Verifying the codebase's implementation status is the best way to handle specification conflicts during archiving. If conflicts are detected, the system applies change specifications chronologically to resolve them, ensuring only implemented modifications are archived.

Can I archive codebase changes that have not been fully implemented yet?▼

You cannot archive unimplemented changes because the system checks the codebase for implementation status first. It ensures that only completed changes are archived, preventing unresolved specifications from cluttering the spec environment.

Why does chronological order matter when resolving spec conflicts in bulk processing?▼

Chronological order matters in spec conflict resolution because it applies earlier change specifications first, establishing a correct sequence of implemented modifications. This prevents overwriting newer changes with older ones during bulk archive operations.

Related Skills

Explore More Software Engineering Skills→
hiro1989hiro1989
1

openspec-bulk-archive-change

Archive multiple completed openspec changes and resolve spec conflicts via codebase analysis.

Community
Advanced
mathiasbourgoinmathiasbourgoin
2

roster-audit

Audit codebases for quality issues and spec compliance with cited findings.

Community
Advanced
PBH-BTNPBH-BTN
6.2k

openspec-bulk-archive-change

Archive multiple completed openspec changes with conflict resolution via codebase inspection.

Official
Advanced
tungnguyen10tungnguyen10

openspec-bulk-archive-change

Batch archive completed openspec changes and resolve delta spec conflicts.

Community
Advanced