Release Eidos Lite, the standalone Eidos CLI, and editor.eidos.space. Use when asked to prepare or publish a Lite or CLI version, write or audit release notes, deploy the Eidos File Web editor, update Lite's bundled Graft dependency, recover a failed release tag, or verify published artifacts and deployments.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Release Eidos Lite, the standalone Eidos CLI, and editor.eidos.space. Use when asked to prepare or publish a Lite or CLI version, write or audit release notes, deploy the Eidos File Web editor, update Lite's bundled Graft dependency, recover a failed release tag, or verify published artifacts and deployments.
Eidos Release
Release one explicit surface at a time. Establish exact inputs, run the
surface-specific gates, create an immutable tag or deployment, monitor the
publisher, and prove the public result.
Lite uses lite-v<semver> and
.github/workflows/build-and-release-eidos-lite.yml.
CLI uses cli-v<semver> and
.github/workflows/build-and-release-cli.yml.
Web deploys independently through Wrangler to editor.eidos.space.
@eidos.space/eidos-file and @eidos.space/eidos-file-ui package publishing
is not implied by any of these releases.
Preserve release invariants
Read root and applicable nested AGENTS.md files first.
Preserve unrelated user changes. Do not stage, format, stash, revert, or
commit them.
Never weaken tests or compatibility assertions to make a release green.
Require the intended branch commit to exist on the remote before tagging.
Use lightweight tags and never move a distributed tag.
For tagged releases, require a curated, non-empty, surface-specific release
body before creating the tag. An empty body, placeholder, or unreviewed
generated commit list is a release blocker.
Treat each checked-in RELEASE_NOTES.md as the body for one version, not as
an accumulating changelog. Replace it completely during release preparation.
Publish that committed body when the GitHub Release is first created. Never
create a generated body and repair it later.
Compare the candidate with the previous three same-surface releases. Reused
feature sections, semantic restatements of an old change, and changes owned
only by another release surface are blockers.
Never claim success from a local tag, green build, or successful deploy
command alone. Prove remote state and public artifacts.
If the worktree contains unrelated changes, leave them untouched and determine
whether the release can proceed safely. Stop if the branch is behind or
diverged unless the user explicitly authorizes another source commit.
Recover an empty failed tag attempt
Recreate a failed tag only when all conditions hold:
The tag was created during the current release attempt.
Its workflow failed.
The failed run has zero uploaded artifacts.
No GitHub Release exists for the tag.
No consumer could reasonably have received the tag.
Prove the conditions before deleting a tag:
gh run view <run-id> --json status,conclusion,headSha,url
gh api repos/<owner>/<repo>/actions/runs/<run-id>/artifacts --jq '.total_count'
gh release view <tag>
Otherwise prepare a new version or prerelease number. Never move a tag with a
Release, artifact, or plausible consumer.
Prove publication
For tagged releases, verify local and remote SHAs, the exact workflow run, the
GitHub Release, its non-empty curated body, expected assets, checksums, and an
installed or packaged smoke. For Web deployments, verify the active Cloudflare
version plus fresh public HTML, service worker, bundle, and user-flow evidence.
Always report the released/deployed commit, tag or deployment ID, public URLs,
validation performed, artifact/platform coverage, and branch/worktree state.
