skills.rest
ConductionNL
ConductionNLOFFICIAL
Explore all skills by this author →
WebsiteGitHub

opsx-bulk-archive

Batch-archive completed code changes by validating artifacts, resolving conflicts, and updating changelogs.

Updated Mar 26, 2026
Search Tags:#automation#workflow#codebase#archive#openspec#conflicts#bulk
One-click install
npx skills add https://github.com/ConductionNL/decidesk --skill opsx-bulk-archive-conductionnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opsx-bulk-archive
Source: https://github.com/ConductionNL/decidesk/tree/main/.claude/skills/opsx-bulk-archive
Command: npx skills add https://github.com/ConductionNL/decidesk --skill opsx-bulk-archive-conductionnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual batch archiving of completed changes is error-prone, inconsistent, and labor-intensive. This skill automates the full lifecycle of archiving multiple changes, including validation, conflict detection, spec synchronization, archive file moves, changelog updates, and optional GitHub issue closure, delivering a reliable, auditable process.

Core Features & Use Cases

  • Batch validation: Gather status for all selected changes.
  • Conflict detection and resolution: Detect overlapping delta specs across changes and resolve by codebase evidence and chronological rules.
  • Archive execution: Move changes to archive folder with date-based naming, preserve original metadata.
  • Documentation updates: Update CHANGELOG.md and linked feature docs; optionally close GitHub issues.
  • Status reporting: Provide a consolidated summary and per-change statuses.

Quick Start

Select all completed changes and confirm the batch to start the automated archive process.

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 completed changes in a codebase without manual errors?▼

Batch archiving completed changes automates validation, conflict detection, spec synchronization, archive file moves, and changelog updates to ensure a consistent, auditable codebase state.

How does conflict resolution work when archiving overlapping delta specs?▼

Conflict resolution for overlapping delta specs detects inconsistencies across selected changes and resolves them using codebase evidence and chronological rules before moving files to the archive.

Can I update the changelog and close GitHub issues during bulk archiving?▼

Bulk archiving supports updating CHANGELOG.md and linked feature docs, and optionally closes linked GitHub issues to reflect archived items in a consolidated summary.

What is the best way to automate moving completed changes to an archive folder?▼

Automating archive execution moves completed changes to an archive folder with date-based naming while preserving original metadata, ensuring reliable and traceable file organization.

Do I need to validate artifacts and check tasks before archiving completed changes?▼

Validating artifacts and checking tasks are required prerequisites for batch archiving, ensuring every selected change meets completion criteria before moving files and updating documentation.

Related Skills

Explore More Software Engineering Skills→
thelegendtubaguythelegendtubaguy
33

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta-spec synchronization.

Community
Advanced
rafazafarrafazafar

openspec-archive-change

Archive completed OpenSpec changes to a date-stamped directory after validation.

Community
Advanced
mrgeoffrichmrgeoffrich
3

ship-it

Merge reviewed GitHub pull requests and update issue statuses.

Community
Intermediate
pabloimrik17pabloimrik17

openspec-bulk-archive-change

Archive multiple openspec changes with conflict detection and resolution.

Community
Advanced