openspec-bulk-archive-change

Archive multiple completed changes and resolve capability spec conflicts via codebase inspection.

133|23|Updated Mar 23, 2020
One-click install
npx skills add https://github.com/aehrc/pathling --skill openspec-bulk-archive-change-aehrc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/aehrc/pathling/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/aehrc/pathling --skill openspec-bulk-archive-change-aehrc

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 by intelligently handling potential conflicts and ensuring only implemented features are archived.

Core Features & Use Cases

  • Batch Archiving: Archive several changes simultaneously, saving time and effort.
  • Conflict Resolution: Automatically detects and resolves conflicts in capability specifications by checking actual codebase implementation.
  • Status Summarization: Provides a clear overview of each change's status, including artifacts, tasks, and spec conflicts.
  • Use Case: When you have finished work on multiple features related to authentication and API updates, use this skill to archive them all at once, ensuring that spec conflicts are resolved correctly before archiving.

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 git changes at once without spec conflicts?

Batch archiving handles completed feature changes by validating task completion and resolving capability spec conflicts agentically. It inspects actual codebase implementation, displays a consolidated status table, and executes the archive command for multiple changes simultaneously.

How does batch archiving verify codebase implementation before archiving changes?

Batch archiving detects capability spec conflicts and resolves them agentically by inspecting the actual codebase implementation. It validates artifact and task completion before displaying a consolidated status table and executing the archive command.

What is the best way to resolve capability spec conflicts when archiving version control changes?

Agentic codebase inspection resolves capability spec conflicts by detecting discrepancies across active changes and verifying actual implementation. This ensures only completed features proceed through the batch archive operation.

Can I review the status of multiple changes before confirming a batch archive operation?

The system displays a consolidated status table showing artifacts, tasks, and spec conflicts for each change before executing the batch archive. It prompts you for selection and confirmation, ensuring you can review all active changes prior to committing the operation.

Do I need to manually check task completion before archiving multiple code changes?

Manual task completion checks are unnecessary because batch archiving automatically validates artifact and task completion for each selected change. It ensures only fully implemented features proceed to the archive command execution.