openspec-bulk-archive-change

Archive multiple completed spec changes and resolve conflicts via codebase inspection.

43|24|Updated Jul 3, 2018

Search Tags:#codebase analysis #archive #openspec #changes #spec conflicts #batch operation

Ready to run

npx skills add https://github.com/tsedio/tsed-cli --skill openspec-bulk-archive-change-tsedio

💬 Prompt for ChatGPT / Claude Chat▼

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

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 automating the identification, validation, and archiving of spec changes, especially when dealing with parallel development efforts.

Core Features & Use Cases

Batch Archiving: Archive several completed changes in a single operation.
Intelligent Conflict Resolution: Automatically detects and resolves spec conflicts by examining codebase implementations.
Use Case: When you have finished work on several related features, this skill allows you to archive them efficiently, ensuring that spec conflicts are handled correctly based on actual code implementation.

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

You can archive multiple completed changes by running a batch operation that lists active changes, prompts for selection, validates task completion, resolves spec conflicts, and executes the archive command after confirmation.

How are spec conflicts handled when archiving changes in parallel development?▼

Spec conflicts are resolved agentically by investigating the codebase to check implementation status, automatically detecting capability spec conflicts during the batch archive and examining the actual code to resolve them correctly.

What is the process for validating artifact and task completion before archiving?▼

Validating artifact and task completion involves listing active changes, prompting user selection, checking completion status, detecting capability spec conflicts, displaying a consolidated status table, and confirming the batch operation before execution.

Can I archive changes if there are capability spec conflicts in the codebase?▼

Yes, capability spec conflicts are handled intelligently during archiving by checking the codebase for actual implementation status and resolving conflicts agentically before displaying a consolidated status table and executing the batch archive.

What does the consolidated status table show during batch archiving?▼

The consolidated status table displays validation results for artifact and task completion alongside detected spec conflicts and their resolution status, allowing you to confirm the batch archive operation before execution.

When should I use batch archiving instead of archiving changes individually?▼

Batch archiving is ideal when you have finished work on several related features in parallel development and need to archive them efficiently, ensuring spec conflicts are handled correctly based on actual codebase implementation.