Verified:GitHub

corgispec-archive-change

Archive completed OpenSpec changes after validating artifacts and syncing GitLab workflow states.

113|9|Updated Apr 30, 2026

Search Tags:#archive #spec sync #memory extraction #artifact verification #worktree isolation #gitlab workflow

One-click install

npx skills add https://github.com/ricoyudog/Coding_Corgi_flow --skill corgispec-archive-change

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: corgispec-archive-change
Source: https://github.com/ricoyudog/Coding_Corgi_flow/tree/main/.opencode/skills/molecules/corgispec-archive-change
Command: npx skills add https://github.com/ricoyudog/Coding_Corgi_flow --skill corgispec-archive-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires corgispec-memory-extract, and includes references (resource) components.

What problem does it solve?

It prevents completed AI coding changes from being finalized without verifying artifacts, tasks, spec synchronization, and (when enabled) the corresponding GitLab workflow state.

Core Features & Use Cases

Worktree-aware change resolution: Selects the correct change using openspec list --json, and when isolation is enabled, discovers changes inside registered git worktrees before archiving.
Completion validation and safety checks: Uses openspec status --change ... --json, warns on incomplete artifacts, and optionally checks tasks.md for remaining work.
Delta spec sync and GitLab workflow updates: Assesses whether delta specs exist and prompts for syncing; when .gitlab.yaml is present and glab is available, updates child and parent issue labels to move workflow forward without closing issues.
Long-term memory and wiki extraction (optional): If memory/ and wiki/ exist, extracts reusable patterns and session summaries via corgispec-memory-extract, then syncs wiki logs and indices.
Archival movement and cleanup: Moves the change into openspec/changes/archive/YYYY-MM-DD-<name>/ and removes the git worktree when isolation is active.

Quick Start

Run the corgispec-archive-change skill and provide the change name when you are ready to finalize it, otherwise let it infer or prompt you to select from available changes.

Frequently Asked Questions about corgispec-archive-change

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

FAQPage Schema

How do I archive completed OpenSpec changes with artifact verification?▼

To archive completed OpenSpec changes, the skill validates artifacts and tasks using openspec status, syncs delta specs, and moves the change into the archive directory. This ensures no incomplete work is finalized without passing tracked gates.

What is the best way to sync delta specs and update GitLab workflow states when finalizing a change?▼

Syncing delta specs and updating GitLab workflow states happens during change archival by prompting for spec sync and using glab to update child and parent issue labels. This moves workflow forward without prematurely closing issues.

Does OpenSpec change archival work with git worktree isolation?▼

OpenSpec change archival supports git worktree isolation by discovering changes inside registered worktrees before archiving. After successful archival, the skill automatically removes the associated git worktree to clean up the environment.

How do I extract long-term memory and wiki artifacts from a finished coding session?▼

Extracting long-term memory and wiki artifacts from finished sessions relies on the corgispec-memory-extract dependency. If memory and wiki directories exist, it extracts reusable patterns and session summaries, then syncs wiki logs and indices.

What happens if artifact validation fails during OpenSpec change archival?▼

When artifact validation fails during OpenSpec change archival, the skill warns about incomplete artifacts and optionally checks tasks.md for remaining work. This prevents finalizing changes that have not met all required completion gates.

Do I need glab installed to archive changes and update GitLab issue labels?▼

You need glab installed to update GitLab issue labels during archival, but it is optional and only triggers when .gitlab.yaml is present. Without glab, the skill still archives changes but skips GitLab workflow state updates.