openspec-bulk-archive-change

Batch-archive multiple completed openspec changes with automatic conflict resolution.

1|Updated Nov 3, 2023
One-click install
npx skills add https://github.com/luifertorres/trading-assistant --skill openspec-bulk-archive-change-luifertorres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/luifertorres/trading-assistant/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/luifertorres/trading-assistant --skill openspec-bulk-archive-change-luifertorres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive bulk completed changes into a single operation, reducing manual overhead and ensuring conflicts are detected and managed by inspecting the codebase.

Core Features & Use Cases

  • Batch-archive multiple changes in one pass, with conflict-aware resolution.
  • Analyze deltas and tasks to determine implemented specs and risks before archiving.
  • Preserve history and move changes into an archive directory with date-stamped naming.

Quick Start

Initiate a bulk archive to move all selected changes into the archive, allowing the tool to resolve conflicts automatically.

Frequently Asked Questions about openspec-bulk-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What's the best way to manage multiple parallel openspec changes before archiving them?

Managing multiple parallel changes requires analyzing deltas and tasks to determine implemented specs, then using a batch-archive operation with conflict-aware resolution to safely move them into the archive directory.

How does conflict resolution work when archiving multiple openspec changes at once?

Automatic conflict reconciliation handles overlapping modifications during bulk archival by scanning the codebase, detecting clashes between parallel changes, and managing them automatically so the archive remains consistent without manual intervention.

Can I select specific completed changes to archive or does it process everything automatically?

The bulk-archive process uses user-driven selection, allowing you to choose specific completed changes across openspec for batch archival rather than blindly processing all available changes in the repository.

Does bulk archiving openspec changes preserve configuration files and project history?

Bulk archiving preserves configuration files and moves selected changes into a dedicated archive directory using date-stamped naming conventions, ensuring your project history remains intact and fully traceable.

What's the best way to manage multiple parallel openspec changes before archiving them?

Managing multiple parallel changes requires analyzing deltas and tasks to determine implemented specs, then using a batch-archive operation with conflict-aware resolution to safely move them into the archive directory.