skills.rest
martinsson
martinssonCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Archive multiple completed openspec changes in a single batch operation.

Updated Feb 12, 2026
Search Tags:#archive#code-analysis#conflict-resolution#batch#openspec#change-management#spec-sync
One-click install
npx skills add https://github.com/martinsson/checkin-automation --skill openspec-bulk-archive-change-martinsson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/martinsson/checkin-automation/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/martinsson/checkin-automation --skill openspec-bulk-archive-change-martinsson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a safe, auditable way to archive multiple completed openspec changes at once while ensuring specs are synchronized and conflicts are resolved based on actual code implementation, preventing accidental loss or misalignment of documented requirements.

Core Features & Use Cases

  • Detects active changes and gathers artifact, task, and delta-spec status for each selected change.
  • Builds capability-to-change maps to identify spec conflicts and resolves them by inspecting the codebase for implementation evidence and applying chronological ordering when appropriate.
  • Performs spec synchronization, moves change directories to an archive path with date-stamped names, and reports per-change outcomes including successes, skips, and failures.
  • Use case: archive several parallel changes after a release candidate verification, ensuring only implemented specs are synced and conflicts are handled deterministically.

Quick Start

Use the skill to select multiple openspec changes, validate their status, resolve any spec conflicts by checking the codebase, and archive the confirmed changes in a single batch operation.

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 batch archive completed openspec changes safely?▼

Batch archiving completed openspec changes involves selecting multiple changes, validating artifact and task status, resolving spec conflicts using codebase evidence, synchronizing specs, and moving change directories to a date-stamped archive path.

How does spec conflict resolution work when archiving multiple change branches?▼

Spec conflict resolution during archival builds capability-to-change maps to identify overlaps, inspects the codebase for actual implementation evidence, and applies chronological ordering to resolve conflicts deterministically.

What happens if some changes fail validation during a batch archive operation?▼

When changes fail validation during batch archival, the operation reports per-change outcomes including successes, skips, and failures, ensuring you know exactly which changes were archived and which require attention.

When do I need to coordinate spec synchronization for parallel change branches?▼

Coordinated spec synchronization for parallel change branches is needed when multiple completed changes are ready for archival simultaneously, ensuring only implemented specs are synced to prevent documented requirement misalignment.

Can I archive openspec changes after a release candidate verification?▼

You can archive openspec changes after a release candidate verification by selecting confirmed changes, ensuring only implemented specs are synced, and handling conflicts deterministically before moving them to the archive.

Does batch archiving openspec changes require checking the codebase for implementation evidence?▼

Batch archiving openspec changes requires checking the codebase for implementation evidence to resolve spec conflicts accurately, ensuring documented requirements are synchronized based on actual code implementation.

Related Skills

Explore More Software Engineering Skills→
sanfordzhangsanfordzhang
1

openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict-aware delta-spec handling.

Community
Advanced
GunjanGrungeGunjanGrunge
3

sentinel

Monitor and automatically recover infrastructure failures across Lambda, EC2, Inngest, DynamoDB, ElevenLabs, and S3.

Community
Advanced
pabloimrik17pabloimrik17

openspec-archive-change

Archive completed openspec changes after verifying artifacts and tasks.

Community
Advanced
MaplumeXMaplumeX

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes into dated directories with conflict resolution.

Community
Advanced