Comet Archive logo

Comet Archive

OrganizationPopular
rpamis
comet-archive

Comet Phase 5: Archive. Invoke with /comet-archive. Merge delta specs into main specs with OpenSpec semantics, archive change.

Overview

Publisherrpamis
Repositorycomet
Skill namecomet-archive
Stars
3.1K
Forks
295
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by rpamis on GitHub. Read the source before you install it.

Installation

Install the Comet Archive AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p .claude/skills
cp -r /tmp/comet/eval/local/skills/benchmarks/039-release/comet-classic-039-archive .claude/skills/comet-archive
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Comet Archive in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Comet Archive on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Comet Archive is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Comet Phase 5: Archive (Archive)

Prerequisites

  • Verification passed (Phase 4 complete)
  • Branch handled
  • verify_result: pass in openspec/changes/<name>/.comet.yaml

Steps

0. Output Language Constraint

Archive summaries and lifecycle closure notes must use the language of the user request that triggered this workflow.

0. Entry State Verification (Entry Check)

Execute entry verification:

bash
COMET_ENV="${COMET_ENV:-$(find . "$HOME"/.*/skills "$HOME/.config" "$HOME/.gemini" -path '*/comet/scripts/comet-env.sh' -type f -print -quit 2>/dev/null)}"
if [ -z "$COMET_ENV" ]; then
  echo "ERROR: comet-env.sh not found. Ensure the comet skill is installed." >&2
  return 1
fi
. "$COMET_ENV"
"$COMET_BASH" "$COMET_STATE" check <name> archive

Proceed to Step 1 after verification passes. The script outputs specific failure reasons when verification fails.

1. Final Archive Confirmation (Blocking Point)

After entry verification passes, must follow the comet/reference/decision-point.md protocol to pause and wait for the user to confirm whether to archive immediately. Must not run "$COMET_BASH" "$COMET_ARCHIVE" "<change-name>" before user confirmation.

Before confirmation, show the user a brief summary:

  • Change name
  • Verification report path and result
  • Branch handling status
  • Irreversible actions this archive will perform: merge main specs with OpenSpec delta semantics, annotate design doc / plan, and move the change to the archive directory

The user confirmation question must be presented as a single-select question with these options:

  • "Confirm archive" — immediately run the archive script to complete spec merge and change movement
  • "Needs adjustment or re-verification" — do not archive; run "$COMET_BASH" "$COMET_STATE" transition <change-name> archive-reopen to return to phase: verify, then invoke /comet-verify. If verification confirms fixes are needed, follow /comet-verify's verification-failure decision flow back to /comet-build
  • "Do not archive yet" — do not archive; keep the current phase: archive state and wait for the user to invoke /comet-archive again later

Only after the user selects "Confirm archive" may Step 2 continue. After the user selects "Needs adjustment or re-verification", must first run the archive-reopen state transition; do not edit .comet.yaml manually.

2. Execute Archive

Run the archive script to automatically complete all steps:

bash
"$COMET_BASH" "$COMET_ARCHIVE" "<change-name>"

The script automatically executes:

  1. Entry state validation (phase=archive, verify_result=pass, archived=false)
  2. Design doc frontmatter annotation (archived-with, status)
  3. Plan frontmatter annotation (archived-with)
  4. OpenSpec archive for delta-merge semantics and moving the change to the archive directory
  5. Main spec guard against leaked delta-only section headings
  6. Update archived: true through comet-state transition <archive-name> archived

If script returns non-zero exit code, report error and stop. If script returns zero exit code, archive is complete. The summary X/Y steps succeeded counts real executed steps and does not double-count delta spec sync or document annotation.

The script calls OpenSpec archive to merge ADDED/MODIFIED/REMOVED/RENAMED delta semantics into main specs, then verifies main specs do not contain delta-only section headings.

Use --dry-run flag to preview without executing.

3. Lifecycle Closed Loop

Spec lifecycle completes here:

brainstorming → delta spec → implementation → verification → main spec merge → design doc annotation → archive

Exit Conditions

  • Archive script executed successfully (exit code 0)
  • Archive directory openspec/changes/archive/YYYY-MM-DD-<change-name>/ exists
  • Archived .comet.yaml contains archived: true

The archive script moves openspec/changes/<name>/ to openspec/changes/archive/YYYY-MM-DD-<name>/.

WARNING: After successful archive, do not run "$COMET_BASH" "$COMET_GUARD" <change-name> archive against the old active change name; the active directory no longer exists. Doing so will cause the guard to error with "change directory not found". Archive completeness is determined by script exit code and archived directory state.

Complete

Comet workflow complete. To start new work, invoke /comet or /comet-open.

Context Compression Recovery

Follow comet/reference/context-recovery.md with phase set to archive. If archived: true and archive directory exists, archival is complete — do not re-execute archive operations.

Frequently asked questions

What does the Comet Archive AI skill do?

Comet Phase 5: Archive. Invoke with /comet-archive. Merge delta specs into main specs with OpenSpec semantics, archive change.

Why use Comet Archive on TypingMind?

Because you install it once and use it with any model. Comet Archive is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Comet Archive in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/rpamis/comet/tree/master/eval/local/skills/benchmarks/039-release/comet-classic-039-archive. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Comet Archive?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Comet Archive?

As many as you like. As long as a model supports skills, you can use Comet Archive with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Comet Archive AI skill free?

Yes. It is published on GitHub by rpamis under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇