Add Claude skills to help release the package#229
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9bd3f908ba
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| git pull origin master | ||
| ``` | ||
|
|
||
| Verify the top commit is the release commit (message should be "Release version X.Y.Z"). If it is not, stop and tell the user to ensure the release PR is merged before running this skill. |
There was a problem hiding this comment.
When the release PR is merged with GitHub's normal merge/squash flow, HEAD after git pull is the merge/squash commit, not necessarily the branch commit created in Step 5. This repo's history already has release/version changes landing through merge commits, and this skill creates the PR title as Release X.Y.Z, so a successfully merged release can fail this exact Release version X.Y.Z check and stop before tagging/publishing. Verify the csproj version or that the release commit is contained in the merge instead of requiring the exact HEAD subject.
Useful? React with 👍 / 👎.
|
|
||
| ## Step 1: Confirm Version | ||
|
|
||
| If the user did not supply a version number, read `src/StatsdClient/StatsdClient.csproj` and show the current `<PackageVersion>`. Ask: "Prepare release for X.Y.Z?" and wait for confirmation before proceeding. |
There was a problem hiding this comment.
<Version> when confirming the release
In the current src/StatsdClient/StatsdClient.csproj, there is no <PackageVersion> element; the package version currently comes from <Version>9.0.0</Version>. When a user invokes prepare-release without explicitly supplying a version, this instruction has no value to read or show for confirmation, so the skill cannot determine the current release version before creating the branch. Read <PackageVersion> if present and otherwise fall back to <Version>.
Useful? React with 👍 / 👎.
| ## Step 3: Tag the Release | ||
|
|
||
| ```bash | ||
| git tag X.Y.Z |
There was a problem hiding this comment.
Should we use git directly or instead use gh release create instead? See: https://cli.github.com/manual/gh_release_create
2 participants
Largely following the release process outlined here add a couple of skills.