skills.rest
em-jones
em-jonesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

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

1|Updated Feb 13, 2026
Search Tags:#gitops#archive#conflict resolution#openspec#changes#batch operation
One-click install
npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-bulk-archive-change-em-jones
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/em-jones/staccato-toolkit/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-bulk-archive-change-em-jones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes in a GitOps workflow, preventing clutter and managing spec conflicts intelligently.

Core Features & Use Cases

  • Batch Archiving: Archive several completed changes simultaneously.
  • Conflict Resolution: Automatically detects and resolves spec conflicts by checking codebase implementation.
  • Use Case: When you have finished working on several parallel features, use this skill to clean up your active changes by archiving them in a single, efficient operation.

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 a GitOps workflow?▼

Batch archiving completed changes in a GitOps workflow involves listing active changes, prompting for selection, validating task status, and executing the archive in a single operation with detailed summary reporting.

How does conflict resolution work when archiving multiple spec changes simultaneously?▼

Conflict resolution for batch archiving detects spec conflicts and automatically resolves them by verifying the actual codebase implementation, ensuring only properly implemented changes are archived.

What is the best way to clean up several parallel features after completion?▼

The best way to clean up parallel features is using a batch archive operation that validates artifact and task statuses, checks code for capability conflicts, and displays a consolidated status before execution.

Do I need to manually resolve spec conflicts before batch archiving changes?▼

Manual conflict resolution is not required before batch archiving, as the operation automatically detects capability conflicts and resolves them by checking the codebase to verify implementation status.

Can I review the status of all selected changes before executing a batch archive?▼

Yes, the batch archive operation displays a consolidated status of all selected changes after validating artifacts, checking task completion, and resolving conflicts, requiring your confirmation before execution.

Related Skills

Explore More Software Engineering Skills→
StrayDragonStrayDragon
1

openspec-bulk-archive-change

Archive multiple completed changes and resolve specification conflicts from code implementations.

Community
Advanced
X-McKayX-McKay
3

check-flux-status

Check synchronization status of Flux CD GitOps resources via Kubernetes API.

Community
Intermediate
sgiathsgiath
4

openspec-archive-change

Archive completed openspec changes after validating artifacts and tasks.

Community
Advanced
tungnguyen10tungnguyen10

openspec-bulk-archive-change

Batch archive completed openspec changes and resolve delta spec conflicts.

Community
Advanced