release-easydict

Orchestrates Easydict macOS GitHub Release drafts, publishing, and post-release issue follow-up.

14.4k|735|Updated Nov 15, 2022
One-click install
npx skills add https://github.com/tisfeng/Easydict --skill release-easydict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-easydict
Source: https://github.com/tisfeng/Easydict/tree/main/.agents/skills/release-easydict
Command: npx skills add https://github.com/tisfeng/Easydict --skill release-easydict

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Releasing a new Easydict version involves many error-prone manual steps: building and notarizing the app, curating English release notes from generated changelogs, publishing GitHub Releases, updating appcast and branches, and then finding and closing the issues fixed by each merged PR. This Skill orchestrates that entire lifecycle with deterministic state, validation, and recovery.

Core Features & Use Cases

  • Release lifecycle orchestration: Run draft, publish, release, and resume actions that wrap the repository's release scripts with content curation, remote verification, and run-ID-based recovery.
  • English release notes curation: Capture GitHub-generated notes, translate PR titles into concise English, pick a highlight PR, and apply a validated title and body to the Draft via scripts/release_content.py.
  • Post-release issue follow-up: Use the issue-followup plan|apply|resume namespace to detect issues linked from merged PRs, decide fixed/related/rejected associations with evidence, comment version notifications, and close resolved issues idempotently.
  • Use Case: After merging PRs for version 2.22.0, ask the agent to run the release; it creates a verified Draft with curated English notes, publishes it with merge prechecks and appcast updates, then comments on and closes every issue fixed by the release.

Quick Start

Ask the agent to release Easydict version 2.22.0 on the beta channel, including curated English release notes and follow-up on all issues fixed by the merged PRs.

Frequently Asked Questions about release-easydict

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

FAQPage Schema
How do I publish a GitHub Release for Easydict?

Run the release action with a version, for example release 2.22.0. The skill creates a verified Draft with curated English notes, publishes it after merge prechecks and appcast installation, verifies the remote state, and then runs issue follow-up automatically.

How do I close GitHub issues fixed by a release?

Use the issue-followup apply action with the published version. It collects issues referenced by merged PRs, validates fixes/related/rejected decisions with evidence, posts one idempotent version notification per issue, and closes currently open resolved issues.

What happens if an Easydict release fails midway?

Failed drafts or publishes keep the GitHub Release in Draft state and preserve rollback data. You resume with the asc run ID rather than starting over, and failed issue follow-up never rolls back an already published release.

Does the release skill modify the dev or main branches directly?

Drafts only push a temporary release/sync branch and the version tag through an isolated worktree. Publish performs merge prechecks first, then safely fast-forwards local dev and atomically updates remote dev and main with a lease, never force-pushing or rebasing.

When should I use --replace-draft for a release?

Use it only when you explicitly want to discard and rebuild the current latest unpublished Draft. It increments the build number automatically, rebuilds from the synced local dev branch, and never reuses the old curated notes or issue state.