菜单
Use this skill when publishing an existing Toastty release artifact to GitHub Releases, using already-authored release notes and tagging the recorded release commit.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use this skill when preparing a Toastty app release build, including Ghostty artifact installation, signed DMG creation, and drafting release notes from the recorded release diff.
Use this skill when building, launching, or validating a live Toastty dev/debug/test app instance with runtime isolation, instance.json targeting, local smoke automation, and local or remote GUI validation.
Use this skill when the user asks for /worktree-create or wants to spin the current Toastty thread into a new git worktree and Toastty workspace, optionally run explicit repo setup, persist a handoff or plan file, and launch a new agent session (codex by default) in the new workspace.
Use this skill when listing recent Toastty diagnostics submissions, fetching, saving, or analyzing a submitted Toastty diagnostics report by report ID, or summarizing a local diagnostics JSON file. It retrieves reports through the Toastty diagnostics Worker admin API, summarizes logs, automation audit calls, redaction state, socket health, and avoids exposing admin secrets or dumping full log bodies.
Use this skill when the user explicitly wants to design, generate, or refine a custom Toastty orchestrator skill for a specific workflow, including workflow-specific coordination across Toastty workspaces, panels, managed agents, artifacts, and cooperative workspace scoping.
Use this skill when selecting, running, or reporting Toastty verification after code, project, dependency, build, test, UI/runtime, menu, shortcut, automation, or agent-instruction changes. It chooses the right mix of remote smoke validation, remote xcodebuild tests, local helpers, live GUI checks, Computer Use, and the global qa subagent for deeper user-perspective QA.
| name | toastty-publish |
| description | Use this skill when publishing an existing Toastty release artifact to GitHub Releases, using already-authored release notes and tagging the recorded release commit. |
Use this workflow when the user already has a built Toastty release artifact and drafted release notes and wants to publish it.
Verify that artifacts/release/<version>-<build>/release-metadata.env, ghostty-metadata.env, sparkle-metadata.env, release-notes.md, and Toastty-<version>.dmg all exist and are non-empty, then read the metadata files.
Confirm RELEASE_SOURCE_COMMIT is available in the local clone before publishing.
Confirm the drafted notes at RELEASE_NOTES_PATH do not contain leftover
{{placeholder}} tokens, satisfy the user, and include these exact canonical
lines using values from release metadata:
- Commit: `<RELEASE_GHOSTTY_COMMIT_SHORT>`
- Build flags: `<RELEASE_GHOSTTY_BUILD_FLAGS>`
Run scripts/release/publish-github-release.sh --create-tag to publish a draft by default. Add --publish only when the user wants the release to go live immediately and update the Sparkle appcast.
artifacts/release/<version>-<build>/release-metadata.env, not the current HEAD, to decide what commit gets tagged.artifacts/release/<version>-<build>/sparkle-metadata.env, not ad-hoc shell values, to decide what gets written to the Sparkle appcast.release-metadata.env is the source of truth for:
RELEASE_SOURCE_COMMITRELEASE_NOTES_PATHRELEASE_GHOSTTY_COMMIT_SHORTRELEASE_GHOSTTY_BUILD_FLAGSscripts/release/publish-github-release.sh expects the notes file to exist, be non-empty, and include exact canonical Ghostty commit and build-flags lines before publication.artifacts/release/<version>-<build>/ must remain intact from the earlier build phase.RELEASE_SOURCE_COMMIT is reachable in the local clone.RELEASE_NOTES_PATH, is non-empty, and includes the exact canonical Ghostty commit and build-flags lines from release metadata.--dry-run when you want to inspect the derived git and gh commands before creating the tag or release.