skills.rest
knopki
knopkiCOMMUNITY
Explore all skills by this author →
𝕏@knopkiGitHub

openspec-bulk-archive-change

Archive multiple completed changes after validating artifact status and resolving spec conflicts.

1|Updated Jun 18, 2025
Search Tags:#archive#conflict resolution#batch#openspec#changes#spec management
One-click install
npx skills add https://github.com/knopki/dotfiles --skill openspec-bulk-archive-change-knopki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/knopki/dotfiles/tree/main/home/private_dot_config/opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/knopki/dotfiles --skill openspec-bulk-archive-change-knopki

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes, intelligently handling potential conflicts by verifying implementation in the codebase.

Core Features & Use Cases

  • Batch Archiving: Archive several changes simultaneously, reducing manual effort.
  • Conflict Resolution: Automatically detects and resolves spec conflicts by checking actual code implementation.
  • Use Case: When you have finished work on several related features, use this Skill to archive them all efficiently, ensuring spec consistency.

Quick Start

Use the openspec-bulk-archive-change skill to archive all completed changes.

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 changes at once to avoid manual effort?▼

You can archive multiple changes at once by batch processing completed features, validating artifact status and delta specs before execution to ensure spec consistency and reduce manual overhead.

How does batch spec archiving resolve conflicts when merging changes?▼

Batch spec archiving resolves conflicts by inspecting the codebase for actual implementation evidence, validating task completion, and intelligently merging specs to ensure the archived changes reflect the true code state.

What is the best way to archive several related features while ensuring spec consistency?▼

The best way to archive related features is using a bulk operation that validates artifacts, checks delta specs, and provides a consolidated status report before execution to ensure spec consistency across all changes.

Can I validate task completion and artifact status before archiving spec changes?▼

Yes, you can validate task completion, artifact status, and delta specs before archiving by generating a consolidated status report, ensuring only fully completed changes are processed in the batch.

What should I check before doing a bulk archive of spec changes?▼

Before a bulk archive of spec changes, you should check artifact status, task completion records, and delta specs, reviewing the consolidated status report to verify implementation evidence exists in the codebase.

Related Skills

Explore More Software Engineering Skills→
arestivoarestivo

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes while resolving delta-spec conflicts.

Community
Advanced
ladislasladislas
2

pac-openspec-archive-change

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

Community
Advanced
inflexa-aiinflexa-ai
29

openspec-bulk-archive-change

Batch archive development changes with spec synchronization and conflict resolution.

Official
Advanced
tungnguyen10tungnguyen10

openspec-bulk-archive-change

Batch archive completed openspec changes and resolve delta spec conflicts.

Community
Advanced