comet-archive

Archives verified OpenSpec changes by merging delta specs and committing the archive.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill comet-archive-shrek-abaper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-archive
Source: https://github.com/shrek-abaper/sap-nexus-agent/tree/main/.comet/skills/skills/comet-archive
Command: npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill comet-archive-shrek-abaper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec-based workflow requires merging delta specs into main specs, annotating design documents, moving the change directory, committing exact paths, and delivering the branch remotely. Doing this manually risks inconsistent state, mixed commits, and skipped confirmations. ## Core Features & Use Cases - Guarded Archive Execution: Runs entry-state verification (phase, verify_result, confirmation flags) before any archive operation, and blocks on mismatched bound branches. - Delta Spec Merge: Invokes OpenSpec archive to merge ADDED/MODIFIED/REMOVED/RENAMED delta semantics into main specs, with a guard against leaked delta-only section headings. - Controlled Delivery: Requires explicit user confirmation before archiving, then commits only attributable paths and pushes or creates a PR per the user's selected delivery method. - Use Case: After verification passes on a change branch, invoke /comet-archive to confirm delivery, merge the delta specs into main specs, create the single archive commit, and push the bound branch or open a PR. ## Quick Start Ask the assistant to run /comet-archive for the verified change to confirm archiving, merge its delta specs, and push the archive commit.

Frequently Asked Questions about comet-archive

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

FAQPage Schema
How do I archive an OpenSpec change after verification?▼

Invoke /comet-archive after Phase 4 verification passes. The skill runs entry-state checks, asks you to confirm delivery, then executes the archive script that merges delta specs into main specs and moves the change to the archive directory.

What does the OpenSpec archive step do to delta specs?▼

The archive script merges ADDED, MODIFIED, REMOVED, and RENAMED delta semantics into the main specs, then verifies main specs contain no delta-only section headings. It also annotates the design doc and plan frontmatter with archive metadata.

Can I archive a change without pushing or creating a PR?▼

Yes. Select "Do not archive yet" at the confirmation prompt to keep the change active with phase archive and branch_status pending. Local merge or postponed push is not offered after archiving; you must choose before the archive runs.

Why is the archive blocked with a BLOCKED branch error?▼

The bound_branch recorded in the change state does not match the current branch. Either switch back to the bound branch and rerun entry verification, or explicitly confirm a rebind with comet state rebind before proceeding.

What happens if the archive commit or push fails?▼

The skill stops, reports the error, and retains the recorded delivery selection. Within the same task it retries only the failed push or PR creation; it never switches, deletes, or rebases branches automatically.