openspec-bulk-archive-change

Archive multiple completed openspec changes while resolving spec conflicts against codebase implementation.

7|3|Updated Dec 24, 2023
One-click install
npx skills add https://github.com/Pony-Unicorn/react-template --skill openspec-bulk-archive-change-pony-unicorn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/Pony-Unicorn/react-template/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/Pony-Unicorn/react-template --skill openspec-bulk-archive-change-pony-unicorn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes by intelligently handling spec conflicts and validating implementation against the codebase.

Core Features & Use Cases

  • Batch Archiving: Archive several completed changes in a single operation.
  • Conflict Resolution: Automatically detects and resolves conflicts when multiple changes affect the same capability specs by checking the codebase for actual implementation.
  • Use Case: When you have finished several parallel features and need to archive them, this skill helps you do so efficiently, ensuring spec consistency and avoiding manual conflict resolution.

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 in openspec?

Batch archiving completed changes in openspec involves validating implementation against the codebase and resolving spec conflicts automatically. This skill handles multiple parallel development efforts in a single operation to ensure spec consistency.

How does spec conflict resolution work when archiving parallel features?

Spec conflict resolution during archiving works by automatically detecting overlapping capability specs across parallel features and validating them against the actual codebase implementation. This ensures spec consistency without requiring manual conflict resolution.

Do I need the openspec CLI to batch archive completed changes?

Yes, you need the openspec CLI installed to batch archive completed changes. The CLI is required for listing changes, checking their completion status, and synchronizing spec updates during the bulk archiving operation.

What is the best way to archive parallel development efforts in openspec?

The best way to archive parallel development efforts is using bulk archiving to validate implementations against the codebase and resolve spec conflicts automatically. This avoids manual conflict resolution across multiple completed features.

When should I avoid batch archiving multiple changes in version control?

You should avoid batch archiving multiple changes when codebase implementation does not match the expected capability specs. If validation fails during conflict resolution, manual inspection of the parallel features is required before archiving.