openspec-bulk-archive-change

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

2|Updated Nov 14, 2024

Search Tags:#git #version control #archive #openspec #spec management #changeset

Ready to run

npx skills add https://github.com/fkoschi/grind-it --skill openspec-bulk-archive-change-fkoschi

💬 Prompt for ChatGPT / Claude Chat▼

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

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 automating the archiving operation.

Core Features & Use Cases

Batch Archiving: Archive several completed changes in a single operation.
Conflict Resolution: Intelligently resolves conflicts when multiple changes affect the same capability by checking the codebase for actual implementation.
Use Case: When you have finished work on several related features (e.g., authentication, user profiles, and permissions), you can use this skill to archive them all simultaneously, ensuring that spec conflicts are resolved correctly before archiving.

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

To archive multiple completed git changesets at once, use a bulk archiving operation that moves completed changes to an archive directory while resolving spec conflicts by examining the codebase implementation.

What happens when multiple changes affect the same spec during batch archiving?▼

During batch archiving, spec conflicts from multiple changes affecting the same capability are intelligently resolved by checking the codebase for the actual implementation to ensure accurate spec synchronization.

Do I need the openspec CLI to batch archive spec changes?▼

Yes, you need the openspec CLI installed to perform batch archiving, as the process requires it for change management and checking the completion status of your changes.

What is the best way to synchronize specs when archiving related features simultaneously?▼

The best way to synchronize specs when archiving related features simultaneously is to use a bulk archive tool that automatically detects and resolves spec conflicts by verifying actual codebase implementations before moving files.

When should I avoid batch archiving completed changes?▼

You should avoid batch archiving completed changes if individual changes are not fully complete or if the openspec CLI status checks fail, as unresolved spec conflicts could lead to inaccurate codebase synchronization.