openspec-bulk-archive-change

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

Updated May 5, 2022
One-click install
npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-bulk-archive-change-blackbelttechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/BlackBeltTechnology/judo-runtime-core/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-bulk-archive-change-blackbelttechnology

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 in a project, preventing manual effort and potential conflicts when dealing with parallel development streams.

Core Features & Use Cases

  • Batch Archiving: Archive several changes simultaneously.
  • Conflict Resolution: Intelligently handles overlapping changes by checking the codebase for actual implementation.
  • Use Case: When you have finished several related features that were developed in parallel, use this skill to archive them all in one go, ensuring that spec conflicts are resolved correctly based on what's actually in the code.

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

Batch archiving multiple completed changes is done by prompting user selection, validating artifact and task status, and resolving spec conflicts based on code presence before execution.

How does bulk archiving handle overlapping spec conflicts in parallel development?

Spec conflict resolution during bulk archiving checks the codebase to verify actual implementation, intelligently resolving overlapping changes by prioritizing code presence and chronological order.

Can I use batch archiving for changesets developed in parallel streams?

Yes, batch archiving supports parallel development streams by archiving several related changes simultaneously, detecting spec conflicts, and verifying implementation status in the codebase before execution.

What is the best way to resolve openspec changeset conflicts without manual code checks?

The best way to resolve changeset conflicts without manual checks is using bulk archiving, which automatically detects spec conflicts and validates them against actual code implementation and chronological order.

Does bulk archiving validate task and artifact status before execution?

Yes, bulk archiving validates artifact and task status before execution, providing a consolidated status report to ensure only completed changes are archived in the single operation.

When should I not use batch archiving for version control changes?

Batch archiving should not be used when changes are incomplete, as it validates artifact and task status before execution and resolves spec conflicts strictly based on actual code presence.