skills.rest
pertrai1
pertrai1COMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Archive multiple code changes in a repository via CLI with openspec.

Updated Apr 3, 2026
Search Tags:#code changes#repository maintenance#spec conflict resolution#batch archiving#archive management
One-click install
npx skills add https://github.com/pertrai1/open-forge --skill openspec-bulk-archive-change-pertrai1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/pertrai1/open-forge/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/pertrai1/open-forge --skill openspec-bulk-archive-change-pertrai1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of archiving multiple completed changes in your codebase, providing an efficient way to manage and organize historical changes.

Core Features & Use Cases

  • Batch Archiving: Archive multiple completed changes in a single operation.
  • Conflict Handling: Detects and resolves spec conflicts by analyzing the codebase.
  • Status Summary: Provides a consolidated table of all changes' statuses before execution.
  • Conflict Resolution: Intelligently resolves conflicts by checking codebase implementations.
  • User Confirmation: Asks for confirmation before performing the batch operation.
  • Summary Output: Displays a summary of the batch operation, including successful, skipped, and failed changes.

Quick Start

To archive your changes, use the 'openspec-bulk-archive-change' skill.

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 code changes in a single batch operation?▼

Batch archiving multiple completed code changes is automated by verifying implementation status, detecting spec conflicts, and ensuring code integrity before asking for user confirmation to execute the repository maintenance operation.

What is the best way to resolve spec conflicts before archiving repository changes?▼

Spec conflict resolution during archiving is handled by intelligently analyzing the codebase to check implementations, detecting conflicts, and providing a consolidated status summary table of all changes before execution.

Does bulk archiving code changes work with CI/CD workflows?▼

Bulk archiving code changes is designed for CI/CD workflows that require maintaining a historical record, operating under CLI interaction constraints to verify implementation status and ensure code integrity during continuous deployment.

Do I need openspec to batch archive completed changes in my repository?▼

Yes, openspec is a required dependency to batch archive completed changes, as the skill operates under the constraint of CLI interaction and relies on openspec to verify implementation status and manage archive operations.

What happens if some code changes fail during batch archiving?▼

Failed code changes during batch archiving are captured in a summary output displaying successful, skipped, and failed changes, allowing you to review the consolidated status table and resolve detected spec conflicts before re-executing.

Related Skills

Explore More Software Engineering Skills→
081595081595

openspec-propose

Generate proposal.md, design.md, and tasks.md for codebase changes via openspec CLI.

Community
Intermediate
tiankong0101-bytetiankong0101-byte

auto-updater

Automate daily update checks and installation for Clawdbot and installed skills.

Community
Advanced
harqianharqian
1

openspec-bulk-archive-change

Archive multiple completed code changes using the openspec CLI.

Community
Advanced
tungnguyen10tungnguyen10

openspec-bulk-archive-change

Batch archive completed openspec changes and resolve delta spec conflicts.

Community
Advanced