openspec-bulk-archive-change

Archive multiple completed code changes and resolve spec conflicts via CLI.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/gokhantaskan/fastback --skill openspec-bulk-archive-change-gokhantaskan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/gokhantaskan/fastback/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/gokhantaskan/fastback --skill openspec-bulk-archive-change-gokhantaskan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

This Skill provides a streamlined process for archiving multiple completed changes simultaneously, reducing the need for individual operations and ensuring consistency in change management.

Core Features & Use Cases

  • Batch Archiving: Archive multiple changes in a single action, saving time and reducing user error.
  • Spec Conflict Detection: Intelligently handles spec conflicts by checking the codebase for actual implementations.
  • Automated Resolution: Automatically resolves conflicts by comparing delta specs and codebase evidence.
  • User Confirmation: Ensures user oversight by requiring selection confirmation for batch operations.
  • Detailed Reporting: Provides a comprehensive summary of the archiving process, including successful archives, skipped changes, and conflict resolutions.

Quick Start

Archive all completed changes using the 'archive-changes' command.

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 code changes at the same time?

Batch archiving multiple completed code changes requires CLI access to the 'openspec' tool and a functional codebase. The operation automates archiving by inspecting codebase evidence and resolving spec conflicts in a single action.

How does spec conflict resolution work during batch archiving?

Spec conflict resolution works by automatically comparing delta specs against actual codebase implementations. The system inspects the codebase to verify evidence and intelligently resolves conflicts without requiring manual intervention for each individual change.

Can I review which changes will be archived before the batch operation runs?

Yes, the batch archiving process requires user confirmation before executing. You must confirm your selection of completed changes, ensuring user oversight and reducing the risk of archiving unintended codebase modifications.

What do I need to set up before batch archiving changes in my development workflow?

You need a functional codebase and CLI access to the 'openspec' tool installed in your environment. These prerequisites allow the system to inspect actual implementations and resolve spec conflicts during the change management process.

How do I get a summary of archived changes and conflict resolutions?

The batch archiving operation provides detailed reporting after completion. This summary includes comprehensive details on successful archives, skipped changes, and any automated spec conflict resolutions applied during the process.