Add Claude skill for publishing releases #687
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Generated by 🚫 Danger |
mokagio
commented
Jan 21, 2026
| After the rake task pushes the branch, create the PR using `gh`: | ||
|
|
||
| ```bash | ||
| /opt/homebrew/bin/gh pr create \ |
Contributor
Author
There was a problem hiding this comment.
I have gh aliased to git checkout and have instructed my Claude to always use the Homebrew path.
I think it's fine to leave as is. If not found at that path, Claude should try other likely locations itself.
Or, maybe we can use gh here and see what my agent does...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I used this skill to publish https://github.com/wordpress-mobile/release-toolkit/releases/tag/14.0.0
To be precise, I iterated on the skill live while publishing the release.
I particularly like the bit where the agent polls the PR status and then goes on with the GitHub release creation.
One could argue that it might have been more robust to add further automation instead of having an resource intense LLM agent put the steps together. I hear you. This is just an experiment, happy to iterate or drop altogether.