skills.rest
finger-gun
finger-gunOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Batch-archive multiple completed changes with conflict-aware synchronization.

4|2|Updated Aug 27, 2025
Search Tags:#automation#codebase#archive#conflict-resolution#openspec#batch-processing#delta-specs
One-click install
npx skills add https://github.com/finger-gun/sisu --skill openspec-bulk-archive-change-finger-gun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/finger-gun/sisu/tree/main/.kilocode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/finger-gun/sisu --skill openspec-bulk-archive-change-finger-gun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes in a single operation. This skill batches changes, resolving conflicts by inspecting the codebase to determine what's actually implemented.

Core Features & Use Cases

  • Batch-archive multiple changes at once with automatic conflict handling.
  • Detect conflicts across delta specs and apply deterministic resolutions based on implementation evidence and change chronology.
  • Preserve metadata and support safe archiving workflows across parallel development streams.

Quick Start

Provide the changes you want archived and let the system batch-archive them with conflict-aware synchronization.

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 batch archive multiple completed codebase changes at once?▼

Batch archive multiple changes by providing them to the system for conflict-aware synchronization. It detects delta spec conflicts, resolves them using implementation evidence, and prompts for confirmation before archiving.

How does conflict resolution work when archiving parallel changes?▼

Conflict resolution for parallel changes inspects the codebase to determine actual implementation and applies established ordering. It detects conflicts across delta specs and applies deterministic resolutions based on change chronology.

Can I archive changes from parallel development streams without losing metadata?▼

Yes, archiving changes from parallel development streams preserves metadata and supports safe archiving workflows. The system enforces deterministic execution to ensure metadata integrity across concurrent changes.

What's the best way to resolve delta spec conflicts during batch archiving?▼

Resolving delta spec conflicts during batch archiving is handled automatically by inspecting the codebase for implementation evidence. The system applies deterministic resolutions based on established ordering and change chronology.

Does batch archiving prompt for confirmation before applying changes?▼

Yes, batch archiving prompts for confirmation before archiving changes. This ensures safe archiving workflows by allowing you to review conflict resolutions and deterministic execution results before finalizing.

When do I need conflict-aware synchronization for archiving codebase changes?▼

Conflict-aware synchronization is needed when archiving multiple completed changes from parallel development streams. It detects conflicts in delta specs and resolves them by inspecting the codebase for actual implementation evidence.

Related Skills

Explore More Software Engineering Skills→
guillaumejayguillaumejay

openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict resolution based on codebase evidence.

Community
Advanced
DatTran26DatTran26

ck:pdf

Extract text and tables, merge, split, and fill PDF forms.

Community
Intermediate
inflexa-aiinflexa-ai
29

openspec-bulk-archive-change

Batch archive development changes with spec synchronization and conflict resolution.

Official
Advanced
tungnguyen10tungnguyen10

openspec-bulk-archive-change

Batch archive completed openspec changes and resolve delta spec conflicts.

Community
Advanced