comet-archive

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill comet-archive-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-archive
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/comet-archive
Command: npx skills add https://github.com/JhonMA82/api-starter --skill comet-archive-jhonma82

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 to an archive directory, committing exact paths, and delivering the branch remotely — a multi-step process that is error-prone when done manually. ## Core Features & Use Cases - Confirmed Archive Execution: Pauses for explicit user confirmation before running the archive, with options to push, push and create a PR, re-verify, or postpone. - Delta Spec Merging: Runs the OpenSpec archive to merge ADDED/MODIFIED/REMOVED/RENAMED delta semantics into main specs and guards against leaked delta-only headings. - Exact-Path Commit and Delivery: Stages only paths attributable to the change, creates a single archive commit, then pushes the bound branch or creates a PR per the user's confirmed choice. - Use Case: After verification passes on a feature change, invoke /comet-archive to confirm delivery, merge the delta specs into main specs, commit the archive, and open a PR — closing the full spec lifecycle. ## Quick Start Invoke /comet-archive after verification passes to confirm archiving, merge the delta specs, commit the archive, and push the branch.

Frequently Asked Questions about comet-archive

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

FAQPage Schema
How do I archive a completed OpenSpec change?▼

Invoke /comet-archive after verification passes. The skill verifies entry state, asks you to confirm archive and delivery, runs the comet archive command to merge delta specs into main specs, commits exact paths, and pushes the branch or creates a PR.

What happens to delta specs during OpenSpec archive?▼

The archive script merges ADDED, MODIFIED, REMOVED, and RENAMED delta semantics into the main specs, then moves the change directory to a dated archive root. It also guards against delta-only section headings leaking into main specs.

Can I preview the archive before executing it?▼

Yes, the archive script supports a --dry-run flag to preview the operation without executing it. You can also choose 'Do not archive yet' at the confirmation step to keep the change active and return later.

What if verification needs to be re-run before archiving?▼

Select 'Needs adjustment or re-verification' at the confirmation prompt. The skill runs the archive-reopen state transition to return to the verify phase, then invokes /comet-verify, which can route back to /comet-build if fixes are needed.

Why does the archive commit only stage specific paths?▼

Staging exact pathspecs prevents mixing pre-existing dirty worktree changes into the archive commit. The skill compares git status against a pre-archive attribution baseline and stops if any path cannot be attributed to the change.

What happens if the push or PR creation fails after archiving?▼

The archive commit remains on the branch and the selection record is retained. The skill retries only the failed push or PR creation within the current task and never switches, deletes, or rebases branches automatically.