skills.rest
rustyrazorblade
rustyrazorbladeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed openspec changes with date-stamped directories after user confirmation.

38|11|Updated Apr 7, 2020
Search Tags:#workflow#version control#archive#change management#openspec#spec sync
One-click install
npx skills add https://github.com/rustyrazorblade/easy-db-lab --skill openspec-archive-change-rustyrazorblade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/rustyrazorblade/easy-db-lab/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/rustyrazorblade/easy-db-lab --skill openspec-archive-change-rustyrazorblade

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you finalize and archive completed changes within an experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

  • Workflow Archiving: Moves completed changes to an archive directory.
  • Status Checks: Verifies artifact and task completion before archiving.
  • Spec Syncing: Assesses and optionally syncs delta specs with main specs.
  • Use Case: After implementing a new feature and testing it thoroughly, use this Skill to archive the associated change, marking it as complete and moving its files to a designated archive location.

Quick Start

Use the openspec-archive-change skill to archive the change named 'new-user-authentication'.

Frequently Asked Questions about openspec-archive-change

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

FAQPage Schema
How do I archive a completed change in an experimental workflow?▼

To archive a completed change, this skill verifies that all artifacts and tasks are finalized, assesses delta spec synchronization, and prompts for confirmation before moving the change to a date-stamped archive directory.

What is the best way to sync delta specs before archiving a change?▼

Before archiving a change, the skill assesses delta spec synchronization and uses the openspec CLI to check status and optionally sync delta specs with main specs to ensure project history is clean.

Do I need openspec-cli to archive completed workflow changes?▼

Yes, you need the openspec CLI installed and available, as the skill requires it to perform status checks and potential spec synchronization during the change archiving process.

Can I automatically move completed feature changes to an archive directory?▼

Yes, the skill moves completed changes to an archive directory using a date-stamped name, but it first prompts for user confirmation to ensure all associated artifacts and tasks are truly finalized.

What happens if artifacts or tasks are not finalized when archiving a change?▼

When archiving a change, the skill performs status checks to verify artifact and task completion, ensuring incomplete work is identified before moving files to the archive directory.

Why does the archive use a date-stamped directory name for completed changes?▼

The archive uses a date-stamped directory name to organize completed changes chronologically, ensuring a clean and easily traceable project history within the experimental workflow.

Related Skills

Explore More Software Engineering Skills→
wonderslifewonderslife
13

openspec-archive-change

Archive completed OpenSpec changes with date-based names and metadata.

Community
Advanced
Charles5277Charles5277
45

openspec-archive-change

Archive completed openspec changes into date-stamped directories after verifying artifacts and tasks.

Community
Advanced
Pony-UnicornPony-Unicorn
7

openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

Community
Advanced
utekutek

git

Manage code changes and repository history with Git commands.

Community
Intermediate