spx-archive

Name: spx-archive
Availability: InStock
Author: Null

Archive completed openspec changes with status checks and delta-spec syncing.

9|9|Updated Mar 24, 2026

Search Tags:#automation #git #cli #archive #openspec #change-management #spec-sync

Ready to run

npx skills add https://github.com/nullmastermind/viber-router --skill spx-archive

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spx-archive
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/spx-archive
Command: npx skills add https://github.com/nullmastermind/viber-router --skill spx-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates finalizing and archiving completed changes in an openspec-based experimental workflow so teams don't leave stale change directories or miss syncing delta specs before archival.

Core Features & Use Cases

Smart change resolution: auto-selects the target change from an explicit name, recent conversation context, or a single active change list, and only prompts when truly ambiguous.
Completion checks and warnings: runs openspec status and inspects task files to surface incomplete artifacts and tasks in a consolidated summary without blocking the archive.
Spec delta syncing: detects delta specs and automatically invokes the project sync process (openspec-sync-specs) to reconcile main specs before archiving.
Safe archive workflow: copies the change into openspec/changes/archive/YYYY-MM-DD-<name>/, preserves .openspec.yaml, and deletes the original directory using guarded commands while failing if the target exists.
Use case: When a developer finishes a feature change, run this Skill to ensure specs are synced, gather warnings, and move the change into an audited archive directory.

Quick Start

Archive the change named "payment-rewrite" and produce a consolidated summary including any warnings and the archive path.

Frequently Asked Questions about spx-archive

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

FAQPage Schema

How do I archive completed changes in an openspec workflow?▼

To archive openspec changes, the workflow resolves the target change, verifies completion status, syncs delta specs, and safely relocates the directory into openspec/changes/archive/YYYY-MM-DD-<name> while preserving .openspec.yaml.

What happens if openspec delta specs are out of sync before archiving?▼

When delta specs are detected, the archive process automatically invokes openspec-sync-specs to reconcile main specs before archiving, ensuring no spec changes are lost during the directory relocation.

How do I finalize an experimental git change set without leaving stale directories?▼

Finalizing an experimental git change set involves running completion checks, syncing specs, and moving the change directory into an audited archive folder, which prevents stale active change directories from accumulating in the repository.

Does the openspec archive process block if tasks are incomplete?▼

The archive process does not block if tasks are incomplete; it runs openspec status to inspect task files and surfaces incomplete artifacts in a consolidated warning summary, but proceeds with the archive.

Can I archive a specific openspec change if multiple active changes exist?▼

You can archive a specific openspec change by providing an explicit name; if multiple active changes exist and no name is given, the Skill only prompts when the target is truly ambiguous, otherwise using conversation context.