corgispec-gh-archive

Archive completed Coding Corgi Flow changes while syncing GitHub issue labels.

113|9|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/ricoyudog/Coding_Corgi_flow --skill corgispec-gh-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: corgispec-gh-archive
Source: https://github.com/ricoyudog/Coding_Corgi_flow/tree/main/.opencode/skills/molecules/corgispec-gh-archive
Command: npx skills add https://github.com/ricoyudog/Coding_Corgi_flow --skill corgispec-gh-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you finalize and archive an implemented change without losing track of what completed, whether specs are synced, or how related GitHub issues should be updated.

Core Features & Use Cases

  • Change completion validation: checks artifact completion and warns about incomplete tasks to reduce “archive-by-accident.”
  • Delta spec sync assessment: detects whether delta specs exist and prompts whether to sync before archiving.
  • GitHub issue lifecycle updates (optional): when openspec/changes/<name>/.github.yaml exists, it updates parent/child issue labels to reflect completion (done) without closing issues.
  • Workflow-preserving archive: moves the full change directory into openspec/changes/archive/YYYY-MM-DD-<name>/ while preserving .openspec.yaml and .github.yaml.
  • Worktree isolation cleanup: if enabled, removes the worktree while preserving the branch for PR-based integration.

Quick Start

Archive your completed change named add-user-auth by running corgispec gh-archive add-user-auth.

Frequently Asked Questions about corgispec-gh-archive

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

FAQPage Schema
How do I archive completed GitHub issues and code changes without losing track of specs?

To archive completed GitHub issues and changes safely, this workflow validates task completion, assesses delta specs, and moves the change directory to an archive path while updating issue labels via GitHub CLI.

What is the best way to sync GitHub issue labels when finalizing a development workflow?

Syncing GitHub issue labels during finalization is handled by optionally reading a .github.yaml file and updating parent and child issue labels to reflect completion without closing the issues entirely.

How do I check if a change is complete before moving it to an archive directory?

Checking change completion before archiving involves validating artifact completion through openspec status and tasks.md, which warns you about incomplete tasks to prevent accidental archival of unfinished work.

Can I use worktree isolation when archiving a change and still preserve my branch?

Worktree isolation can be used during archiving to clean up the working directory while preserving the underlying branch for pull request-based integration into your main codebase.

Does archiving delta specs delete my openspec configuration files?

Archiving delta specs does not delete configuration files; the safe directory move preserves both .openspec.yaml and .github.yaml files within the dated archive folder structure.

Why does my archived GitHub issue remain open after the change directory is moved?

Archived GitHub issues remain open because the workflow applies guarded label transitions to mark completion status rather than automatically closing the issue, leaving final closure for manual review.