Menü
Draft a new release of the project.
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.
Basierend auf der SOC-Berufsklassifikation
Form an Agent Team of Implementer and Reviewer subagents to tackle the given task, looping implementation and review until the Reviewer reports zero high-or-above findings and no more than three mid findings.
Approve a pull request using gh pr review --approve
Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed), get every check green, and merge. Use when the user wants to shepherd a Dependabot bump PR to merge.
Resolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the `goal-pr` skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.
Resolve every open maintainer-scrap issue one at a time: fact-check each with web research, close the ones that need no action, and run the `goal-pr` skill to fix, review, and merge the ones that do — repeating until no actionable scrap issues remain.
Batch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.
| name | draft-release |
| description | Draft a new release of the project. |
| targets | ["*"] |
First, let's work on the following steps.
What's Changed, Contributors and Full Changelog are needed../tmp/release-notes/*.md will be used as the release notes.Then, from $ARGUMENTS, get the new version without v prefix, and assign it to $new_version. For example, if $ARGUMENTS is "v1.0.0", the new version is "1.0.0".
If $ARGUMENTS is empty, determine the new version automatically by performing the release-dry-run skill.
Let's resume the release process.
git pull.git checkout -b release/v${new_version}.getVersion() function to return the ${new_version} in src/cli/index.ts, and run pnpm cicheck. If the checks fail, fix the code until pass. Then, execute git add, git commit and git push.pnpm version ${new_version} --no-git-tag-version.package.json will be modified, execute git commit and git push.getVersion() in src/cli/index.ts is updated to the ${new_version}.gh pr create to the main branch.gh release create v${new_version} --draft --title v${new_version} --notes-file ./tmp/release-notes/*.md command on the github.com/dyoshikawa/rulesync repository. This creates a draft release so that the publish-assets workflow can upload assets later.Note: the Homebrew tap formula (Formula/rulesync.rb) is NOT updated here. It embeds sha256 checksums of the release binaries, which only exist after the release PR merges and the Publish Assets workflow uploads them. The goal-release skill performs that update as its post-merge step (regenerate with scripts/generate-homebrew-formula.ts from the release's SHA256SUMS and land it via an immediately merged PR). When releasing manually without the goal-release skill, run that step yourself after the assets are published.