skills.rest
fjpulidop
fjpulidopCOMMUNITY
Explore all skills by this author →
GitHub

opsx-bulk-archive

Batch-archive multiple completed changes under date-named directories while preserving .openspec.yaml files.

9|2|Updated Mar 12, 2026
Search Tags:#automation#workflow#codebase#archive#openspec#conflicts#bulk-archive
One-click install
npx skills add https://github.com/fjpulidop/specrails-core --skill opsx-bulk-archive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opsx-bulk-archive
Source: https://github.com/fjpulidop/specrails-core/tree/main/specrails-plugin/skills/opsx-bulk-archive
Command: npx skills add https://github.com/fjpulidop/specrails-core --skill opsx-bulk-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Archives multiple completed changes in a single operation, preserving history and reducing manual overhead.

Core Features & Use Cases

  • Batch-archive changes and reconcile spec conflicts by inspecting the codebase.
  • Resolve conflicts deterministically by applying implemented specs in a defined order.
  • Provide a consolidated status before confirming archival, with an auditable record.

Quick Start

Initiate a bulk archive for active changes and let the tool guide you through selection, conflict resolution, and archival.

Frequently Asked Questions about opsx-bulk-archive

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

FAQPage Schema
How do I batch archive multiple completed changes in an OpenSpec codebase?▼

Batch archiving multiple changes streamlines project cleanup by archiving parallel changes in a single operation. It validates statuses, resolves spec conflicts deterministically, and prompts for confirmation before archiving into date-named directories.

How does conflict resolution work when archiving parallel changes?▼

Conflict resolution during archival applies implemented specs in a defined order to deterministically reconcile conflicts. The tool inspects the codebase, applies per-conflict resolution rules, and provides a consolidated status before confirming the archival operation.

Can I preserve the .openspec.yaml file when archiving completed changes?▼

Yes, bulk archiving preserves the .openspec.yaml file while moving completed changes into date-named directories. This ensures project history and configuration remain intact and auditable after the batch archival operation finishes successfully.

What is the best way to streamline project cleanup for multiple OpenSpec changes?▼

Bulk archiving streamlines project cleanup by reconciling spec conflicts and validating statuses before moving changes. It provides a consolidated status, prompts for confirmation, and preserves history in date-named directories for an auditable record.

Do I need to confirm before archiving changes in a bulk operation?▼

Yes, the tool prompts for confirmation after validating statuses and resolving conflicts. It provides a consolidated status summary before proceeding, ensuring you review the batch archival operation and maintain an auditable record of the changes.

Related Skills

Explore More Software Engineering Skills→
BlackBeltTechnologyBlackBeltTechnology

openspec-bulk-archive-change

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

Official
Advanced
inspedralbesinspedralbes

openspec-archive-change

Archive completed experimental changes into date-stamped folders after verification.

Official
Advanced
pacaplanpacaplan
30

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes and resolve spec conflicts via codebase analysis.

Community
Advanced
CatsofsufferingCatsofsuffering
5

openspec-bulk-archive-change

Batch archive completed OpenSpec changes with conflict-aware resolution.

Community
Advanced