Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Close out a spec-superflow change with verification, summary, and archive readiness.
Install Release Archivist
$ npx skills add MageByte-Zero/spec-superflow --skill release-archivist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MageByte-Zero/spec-superflow release-archivist --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release-archivist .claude/skills/release-archivist && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-archivist" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/release-archivist into .claude/skills/release-archivist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-archivist", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/release-archivistType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MageByte-Zero/spec-superflow --skill release-archivist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MageByte-Zero/spec-superflow release-archivist --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/release-archivist .agents/skills/release-archivist && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-archivist" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/release-archivist into .agents/skills/release-archivist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-archivist", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MageByte-Zero/spec-superflow --skill release-archivist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MageByte-Zero/spec-superflow release-archivist --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/release-archivist .cursor/skills/release-archivist && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-archivist" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/release-archivist into .cursor/skills/release-archivist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-archivist", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MageByte-Zero/spec-superflow.git --path skills/release-archivist--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MageByte-Zero/spec-superflow --skill release-archivist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MageByte-Zero/spec-superflow release-archivist --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/release-archivist .gemini/skills/release-archivist && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-archivist" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/release-archivist into .gemini/skills/release-archivist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-archivist", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MageByte-Zero/spec-superflow release-archivistInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MageByte-Zero/spec-superflow --skill release-archivist -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/release-archivist .github/skills/release-archivist && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-archivist" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/release-archivist into .github/skills/release-archivist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-archivist", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MageByte-Zero/spec-superflow --skill release-archivist -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MageByte-Zero/spec-superflow release-archivist --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/release-archivist .opencode/skills/release-archivist && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-archivist" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/release-archivist into .opencode/skills/release-archivist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-archivist", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-archivist- GitHub stars
- 841
- Used in
- 1 other repo
- Token cost
- ~1.3k tokens
- SKILL.md length
- 646 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Close out a spec-superflow change with verification, summary, and archive readiness.
- Works in 6 steps: Verify the final code snapshot with… → Check contract coverage, design… → Require the current plan's review… → …
- Development work in your project
- SKILL.md covers Bundled runtime, New direct/planned changes, Bounded paths and Full / legacy Hotfix, plus 1 more section
- Calls node
What it does
Release Archivist is an agent skill from MageByte-Zero/spec-superflow. Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: 源码级融合 OpenSpec 规划引擎 + Superpowers 执行纪律的 AI 编程工作流插件。17 平台支持，9 skills，Spec-first，契约驱动。 The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/release-archivist”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Verify the final code snapshot with required build/test/validation commands. Reuse fresh results only when the code, environment and…
- Check contract coverage, design consistency, scope and unresolved findings against the actual diff. Cite commands/results; do not infer…
- Require the current plan's review policy: one final whole-range review for Native final, or the required wave receipts for wave/legacy…
- Synchronize actual delta specs using spec-merger while executing. If specs were explicitly omitted and no delta exists, don't recreate them.
- Run SSF audit and record verification outcome (dp_6_result, timestamp and test_result). Record DP-7 only with the user's archive…
- With blockers resolved, run SSF state transition closing. This is logical closure; it does not claim merge or cleanup succeeded.
What it can do on your machine
Read from SKILL.md and the folder at commit 25d9b0c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Archivist loads about 1.3k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 646 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from MageByte-Zero/spec-superflow at commit 25d9b0c, republished under its MIT licence (© MageByte-Zero). 646 words, ~1,251 tokens.
Download SKILL.mdSave it as
.claude/skills/release-archivist/SKILL.md (or your agent's skills folder).- name
- release-archivist
- description
- Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
Release Archivist
Bundled runtime
Before executing a CLI line below, replace its leading SSF with node "<plugin-root>/scripts/spec-superflow.mjs"; <plugin-root> is the absolute directory two levels above this file. Never run SSF literally or call an ssf from PATH.
Read SSF resume <change-dir> --json. In executing, complete verification and logical closure. In closing, perform only recorded pending physical finish, if merging is authorized. abandoned or a completed finish requires no work. Other states route through workflow-start.
New direct/planned changes
Use SSF workflow complete <dir> --verification-command "<required check command>". It runs final verification once; do not run the identical full suite immediately before invoking it. Planned execution additionally checks completed tasks, current full-range/wave review and any delta-spec publication. Direct execution needs no plan or review receipt. Ordinary failures stay in executing for focused repair. Do not add DP-6/DP-7 or another approval to authorized code delivery.
If the user explicitly accepts unfinished work or failed verification, use SSF workflow complete <dir> --accept-risk --confirm --reason "<decision and remaining issues>". Preserve every failure and report accepted-risk, not verified success. This ends code delivery without merging or deleting the branch. A plain closing transition cannot bypass failed checks. For verified work, physical integration remains a separate authorized operation. The remaining closure steps are legacy compatibility.
Bounded paths
Quick/direct Hotfix/Tweak record changed files, focused command and result, persist test_result: pass, then transition to closing. Hotfix must prove the original symptom fixed. Lightweight also needs its receipt's focused review and passing verification evidence. These paths require no contract, execution plan, wave reviews, audit, DP-6/DP-7 or SSF finish.
Full / legacy Hotfix
- Verify the final code snapshot with required build/test/validation commands. Reuse fresh results only when the code, environment and command are identical; don't rerun the same full suite just because the skill changed.
- Check contract coverage, design consistency, scope and unresolved findings against the actual diff. Cite commands/results; do not infer success from edits or unchecked claims.
- Require the current plan's review policy: one final whole-range review for Native
final, or the required wave receipts forwave/legacy plans. Do not request a duplicate review of unchanged evidence. - Synchronize actual delta specs using spec-merger while executing. If specs were explicitly omitted and no delta exists, don't recreate them.
- Run
SSF audit <dir>and record verification outcome (dp_6_result, timestamp andtest_result). Record DP-7 only with the user's archive authorization already obtained or explicitly requested. Do not fabricate missing decisions. - With blockers resolved, run
SSF state transition <dir> closing. This is logical closure; it does not claim merge or cleanup succeeded.
Report only the outcome, key verification, unresolved risks and next action. Preserve the approved contract and implementation evidence; don't copy all planning files into a second summary.
Show full SKILL.md (195 more words)Show less
Physical finish
For authorized Full/legacy Hotfix integration, run SSF finish <dir> [--test-cmd <command>]. It uses recorded target checkout/branch, merges if necessary, verifies the target, and safely removes isolation. It verifies an archive of ignored change artifacts and preserves the previous target before cleanup. It never force-removes uncommitted work. Branch-only isolation never deletes the checkout.
Verification failure preserves isolation. For recorded verify-pending, recovery offers the guarded closing -> debugging transition; diagnose, repair within approved scope, reverify and review before closing again. Completed finish and abandoned changes cannot reopen. Cleanup failure remains cleanup-pending. Resume performs the remaining steps; each unfinished finish retry verifies once again because ignored dependencies, local configuration and external services may have changed even at the same HEAD. Completed finish does not rerun verification. Completed finish is idempotent. A missing or ambiguous target is a real blocker: recover provenance before merging, never guess the target from the current directory.
If the user requested branch delivery without merging, leave the branch/worktree intact and report that status. Do not treat logical closure as permission to merge, push or release.
Use SSF state set <change-dir> dp_6_timestamp now and SSF state set <change-dir> dp_7_timestamp now when recording those decisions.
© MageByte-Zero, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/release-archivist of MageByte-Zero/spec-superflow.
Open the folder on GitHubat commit 25d9b0c
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in MageByte-Zero/spec-superflow, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Release Archivist next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Archivist this skillMageByte-Zero/spec-superflow | 841 | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 59 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from MageByte-Zero/spec-superflow
All 9 skills in this repoBug Investigator
MageByte-Zero/spec-superflow
A skill your agent uses when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes.
Need Explorer
MageByte-Zero/spec-superflow
Clarify intent, scope, constraints, and success criteria before artifact creation.
Spec Writer
MageByte-Zero/spec-superflow
Create or refine spec-superflow planning artifacts. An agent skill from MageByte-Zero/spec-superflow.
Build Executor
MageByte-Zero/spec-superflow
Execute an active direct request or approved planned change.
Contract Builder
MageByte-Zero/spec-superflow
Maintain an execution contract only for an existing legacy change that requires one.
Workflow Start
MageByte-Zero/spec-superflow
Primary entry point for the spec-superflow state-machine workflow.
Related
Categories
Questions about Release Archivist
What does Release Archivist do?
Close out a spec-superflow change with verification, summary, and archive readiness. Release Archivist is an agent skill from MageByte-Zero/spec-superflow. Close out a spec-superflow change with verification, summary, and archive readiness.
When should I use Release Archivist?
Release Archivist fits situations like: development work in your project.
How do I install Release Archivist in Claude Code?
Run `npx skills add MageByte-Zero/spec-superflow --skill release-archivist -a claude-code`. Or copy the skill folder (skills/release-archivist in MageByte-Zero/spec-superflow) into .claude/skills/release-archivist in your project. Claude Code loads it when a task matches its description.
How do I install Release Archivist in Codex?
Run `npx skills add MageByte-Zero/spec-superflow --skill release-archivist -a codex`. Or copy the skill folder (skills/release-archivist in MageByte-Zero/spec-superflow) into .agents/skills/release-archivist in your project. Codex loads it when a task matches its description.
Can I use Release Archivist in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MageByte-Zero/spec-superflow --skill release-archivist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-archivist, .gemini/skills/release-archivist, .github/skills/release-archivist and .opencode/skills/release-archivist in your project.
What does Release Archivist need to run?
Going by SKILL.md and its folder, Release Archivist needs the command-line tools its instructions call (node).
Does Release Archivist access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Release Archivist safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Archivist use?
Release Archivist is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Archivist use?
About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Archivist?
Skills that share tags, products or a category with Release Archivist: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Archivist?
MageByte-Zero (a GitHub user) maintains it in MageByte-Zero/spec-superflow, which has 841 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 1, 2026.
Source: MageByte-Zero/spec-superflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.