goal-release
Cut a release end to end: use the `draft-release` skill to open the release PR and draft GitHub release, wait for CI to turn green, run the `merge-pr` skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or triggers on "the `goal-release` skill".
Profile →npx skills add dyoshikawa/rulesync --skill goal-release --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Goal Release new_version = the user's request This skill drives a release all the way to merge. It uses the `draft-release` skill to open the release pull request (and create the draft GitHub release), waits for the PR's CI checks to pass, runs the `merge-pr` skill to merge it, and finally updates the Homebrew tap formula once the release assets are built. ## 1. Draft the Release Use the `draft-release` skill with `new_version`. - If `new_version` is provided (e.g. `v1.2.3` or `1.2.3`), it must match the semver shape `^v?\d+\.\d+\.\d+$` — if it does not, stop and report instead of passing it on. Pass a valid value through unchanged; the `draft-release` skill normalizes the `v` prefix itself. - If `new_version` is empty, pass no argument; the `draft-release` skill determines the next version automatically via the `release-dry-run` skill. When the `draft-release` skill finishes, it has: - created a `release/v<version>` branch with the version-bump commits, - opened a pull request against `main`, and - created a draft GitHub release `v<version>` with the release notes. If the `draft-release` skill failed partway (e.g. the PR exists but the draft release was not created, or it stoppe
- 1. Draft the Release
- 2. Resolve the Release PR
- 3. Wait for CI
- 4. Merge the Release PR
- 5. Update the Homebrew Formula
- 6. Final Report
gh pr view --json number,title,state,headRefName gh pr checks <pr_number> --watch gh run list --workflow "Publish Assets" --branch "release/v<version>" \ gh run watch <run_id> gh release view v<version> --json isDraft --jq .isDraft git checkout main && git pull gh release download v<version> --pattern SHA256SUMS --dir ./tmp --clobber pnpm exec tsx scripts/generate-homebrew-formula.ts <version> ./tmp/SHA256SUMS Formula/rulesync.rb rm -f ./tmp/SHA256SUMS git switch -c homebrew-formula/v<version>
What does the goal-release skill do?
Cut a release end to end: use the `draft-release` skill to open the release PR and draft GitHub release, wait for CI to turn green, run the `merge-pr` skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or triggers on "the `goal-release` skill".
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill goal-release --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.