skills.rest
Soju06
Soju06COMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Archive multiple completed changes while resolving spec conflicts via codebase inspection.

2.6k|399|Updated Jan 7, 2026
Search Tags:#git#version control#code management#archiving#openspec#spec conflicts
One-click install
npx skills add https://github.com/Soju06/codex-lb --skill openspec-bulk-archive-change-soju06
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/Soju06/codex-lb/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/Soju06/codex-lb --skill openspec-bulk-archive-change-soju06

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 changes by intelligently handling potential spec conflicts and ensuring accurate implementation tracking.

Core Features & Use Cases

  • Batch Archiving: Archive several completed changes in a single operation.
  • Conflict Resolution: Automatically detects and resolves conflicts between changes affecting the same capabilities by inspecting the codebase.
  • Intelligent Syncing: Ensures that only implemented specifications are synced before archiving.
  • Use Case: When you have finished work on several parallel features, use this skill to archive them all at once, preventing merge issues and ensuring a clean project history.

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 changes in a single operation?▼

Batch archiving of multiple changes is handled in a single operation by verifying artifact status, task completion, and delta spec analysis to ensure accurate synchronization before moving items to the archive.

How does bulk archiving resolve spec conflicts between parallel features?▼

Spec conflicts are resolved by inspecting the codebase for implementation evidence, intelligently matching delta specs against actual code changes to determine which specifications should be synced and archived.

When do I need to sync specifications before archiving completed changes?▼

Syncing is required before archiving to ensure only implemented specifications are committed, preventing merge issues and maintaining a clean project history across parallel feature branches.

Can I archive several parallel features at once without causing merge issues?▼

Archiving several parallel features simultaneously prevents merge issues by automatically detecting and resolving spec conflicts that affect the same capabilities through codebase inspection.

What is the best way to handle artifact status and task completion during batch archiving?▼

Batch archiving handles artifact status and task completion automatically, inspecting delta spec analysis and implementation evidence to synchronize specifications accurately across all completed changes.

Related Skills

Explore More Software Engineering Skills→
knopkiknopki
1

openspec-bulk-archive-change

Archive multiple completed changes after validating artifact status and resolving spec conflicts.

Community
Advanced
danielsogldanielsogl
39

openspec-bulk-archive-change

Batch-archive completed openspec changes into daily archives with conflict-aware handling.

Community
Advanced
DanielShuguangDanielShuguang

openspec-bulk-archive-change

Archive multiple completed changes while resolving specification conflicts via code analysis.

Community
Advanced
dentedgem9846-clawdentedgem9846-claw

openspec-bulk-archive-change

Batch-archive multiple completed changes with conflict resolution and validation.

Community
Advanced