Github Release
CheckedAutomates GitHub release creation, tagging, and deployment based on provided instructions and version numbers.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add jezweb/claude-skills --skill github-release -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
jezweb
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned jezweb/claude-skills at 1260fa7439.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1260fa7439
- Scanned
- 3 files, 255 lines
About this skill
The github-release skill automates the creation and management of GitHub releases, allowing AI agents to generate release notes, attach assets, and tag versions directly within a repository. It streamlines the deployment workflow by handling the repetitive tasks associated with publishing new software updates.
When to use it
- Automating release notes generation after every successful CI/CD pipeline run.
- Attaching build artifacts or binaries to specific version tags without manual upload.
- Standardizing release metadata across multiple projects in a monorepo structure.
- Triggering release creation based on semantic versioning rules detected in commit messages.
Key capabilities
- Creates new GitHub releases programmatically via API integration.
- Generates structured release notes from changelogs or commit history.
- Uploads assets (archives, executables, documentation) to the release page.
- Manages version tags and draft/release status transitions.
Example prompts
- "Create a new GitHub release for version 2.1.0 with the release notes from the CHANGELOG.md file."
- "Upload the latest build artifact to the current release and mark it as the latest version."
- "Draft a release for the upcoming beta version using the commit messages since the last tag."
Tips & gotchas
Ensure your AI agent has valid GitHub Personal Access Tokens with repo scope permissions before attempting to create releases. Verify that the target repository supports the specific asset formats you intend to upload, as some file types may be restricted by GitHub's policies.