Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Automates software releases from version bump to GitHub release.
Install Paw Tools Release
$ npx skills add pawbytes/skill-suites --skill paw-tools-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pawbytes/skill-suites paw-tools-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/tools/paw-tools-release .claude/skills/paw-tools-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "paw-tools-release" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-release into .claude/skills/paw-tools-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pawbytes/skill-suites --skill paw-tools-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pawbytes/skill-suites paw-tools-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/tools/paw-tools-release .agents/skills/paw-tools-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "paw-tools-release" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-release into .agents/skills/paw-tools-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pawbytes/skill-suites --skill paw-tools-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pawbytes/skill-suites paw-tools-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/tools/paw-tools-release .cursor/skills/paw-tools-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "paw-tools-release" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-release into .cursor/skills/paw-tools-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pawbytes/skill-suites.git --path src/tools/paw-tools-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pawbytes/skill-suites --skill paw-tools-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pawbytes/skill-suites paw-tools-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/tools/paw-tools-release .gemini/skills/paw-tools-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "paw-tools-release" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-release into .gemini/skills/paw-tools-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pawbytes/skill-suites paw-tools-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pawbytes/skill-suites --skill paw-tools-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/tools/paw-tools-release .github/skills/paw-tools-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "paw-tools-release" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-release into .github/skills/paw-tools-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pawbytes/skill-suites --skill paw-tools-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pawbytes/skill-suites paw-tools-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/tools/paw-tools-release .opencode/skills/paw-tools-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "paw-tools-release" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-release into .opencode/skills/paw-tools-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
paw-tools-release- GitHub stars
- 110
- Token cost
- ~782 tokens
- SKILL.md length
- 332 words
- Files
- 9 (incl. scripts, references)
- Skills in repo
- 71
- Repo updated
- First seen
- Licence
- MIT
At a glance
Automates software releases from version bump to GitHub release.
- Works in 3 steps: Git repository — Must be in a git… → GitHub CLI — gh must be installed and… → Clean working tree — Abort if…
- The user requests to create a release
- SKILL.md covers Overview, On Activation, Prerequisites and Workflow, plus 3 more sections
- Runs Python scripts from its folder
What it does
Paw Tools Release is an agent skill from pawbytes/skill-suites. Automates software releases from version bump to GitHub release. Use when the user requests to 'create a release', 'cut a release', 'publish a new version', or 'prepare a release'.
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts and reference files (for example `references/01-validate.md`, `references/02-version.md` and `references/03-changelog.md`).
It sits in Development. It works with GitHub and Git. The repository describes itself as: 50+ AI agent skills for Claude, Codex, OpenClaw etc — agentic marketing automation, AI creative agency, and developer productivity tools. The licence is MIT.
When your agent uses it
- The user requests to create a release
- Publish a new version
- Prepare a release
Example prompts
- “create a release”
- “cut a release”
- “publish a new version”
- “/paw-tools-release”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Git repository — Must be in a git repository with at least one commit
- GitHub CLI — gh must be installed and authenticated for GitHub releases
- Clean working tree — Abort if uncommitted changes exist (warn in headless, prompt in interactive)
What it can do on your machine
Read from SKILL.md and the folder at commit 547a6df. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 4 files in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Paw Tools Release loads about 782 tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 50 tokens; SKILL.md has 332 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from pawbytes/skill-suites at commit 547a6df, republished under its MIT licence (© pawbytes). 332 words, ~782 tokens.
Download SKILL.mdSave it as
.claude/skills/paw-tools-release/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- paw-tools-release
- description
- Automates software releases from version bump to GitHub release. Use when the user requests to 'create a release', 'cut a release', 'publish a new version', or 'prepare a release'.
Release Automation
Overview
This skill automates the complete release workflow: version bumping, changelog generation, git tagging, and GitHub release creation. Act as a release engineer who ensures clean, traceable releases with informative changelogs.
Args: Accepts --headless / -H for non-interactive execution, --version <semver> to specify version explicitly, --branch <name> to set allowed release branch.
Your output: A complete release with updated version files, appended changelog, git tag, and draft GitHub release.
On Activation
Load available config from {project-root}/.pawbytes/config/config.yaml and {project-root}/.pawbytes/config/config.user.yaml if present. If config is missing, continue with sensible defaults.
Extract relevant config keys:
release_default_branch(default: main)communication_language(default: English)
Detect --headless / -H flag. If present, set {headless_mode}=true for all stages and complete the release without user interaction.
Prerequisites
Before starting, verify:
- Git repository — Must be in a git repository with at least one commit
- GitHub CLI —
ghmust be installed and authenticated for GitHub releases - Clean working tree — Abort if uncommitted changes exist (warn in headless, prompt in interactive)
If any prerequisite fails, explain what's needed and offer to help resolve.
Workflow
Load and execute stages sequentially:
- Validate →
./references/01-validate.md - Version →
./references/02-version.md - Changelog →
./references/03-changelog.md - Release →
./references/04-release.md
Each stage specifies its progression condition. If a stage fails, stop and inform the user.
Key Decisions
These guide the executing agent's judgment:
- Version bump logic — If user doesn't specify version, infer from conventional commits:
breaking:→ major,feat:→ minor,fix:/others → patch. When in doubt, ask (or patch in headless). - Branch enforcement — If configured, only allow releases from that branch. In interactive mode, let user override.
- First release handling — If no previous tags exist, include all commits since repository start.
- Pre-release versions — Support
--pre-release beta/rc/alphaflag for pre-release versions.
Output Artifacts
| Artifact | Location |
|---|---|
| Updated version files | Project root (package.json, Cargo.toml, etc.) |
| Changelog entry | {project-root}/CHANGELOG.md |
| Git tag | Pushed to origin |
| GitHub release | Draft, ready to publish |
| Release report | {project-root}/.pawbytes/tools-output/releases/ |
Scripts
./scripts/detect_version_files.py— Finds and parses version files across project types./scripts/parse_commits.py— Parses conventional commits for changelog grouping
Run <script> --help for usage details.
© pawbytes, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files (scripts, references) in src/tools/paw-tools-release of pawbytes/skill-suites.
- SKILL.md
- references/01-validate.md
- references/02-version.md
- references/03-changelog.md
- references/04-release.md
- scripts/detect_version_files.py
- scripts/parse_commits.py
- scripts/tests/test_detect_version_files.py
- scripts/tests/test_parse_commits.py
Open the folder on GitHubat commit 547a6df
Compare with similar skills
Paw Tools Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Paw Tools Release this skillpawbytes/skill-suites | 110 | — | ~782 | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Pull Request Title and Body Writeropeninterpreter/openinterpreter | 69k | 2 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| PR Review State Fetchprisma/orm | 48k | — | ~767 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
- Official
PR Review State Fetch
prisma/orm
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
More from pawbytes/skill-suites
All 71 skills in this repoProdig Suites Setup
pawbytes/skill-suites
Installs the Prodig Suites product-creation module into a project, scaffolding its workspace folders and writing the shared and personal config files.
Video Clip Repurposing
pawbytes/skill-suites
Cuts long-form video into short platform-ready clips: finds strong moments, reframes for vertical, adds subtitles and brand overlays, and writes a clip manifest.
Paw Pa Generation
pawbytes/skill-suites
Assembles branded, export-ready proposals from brief, research, and pricing artifacts — type-adaptive for pitch, RFP, or scoping.
Proposal Brief Intake
pawbytes/skill-suites
Turns pasted text, audio, video or URLs from a client into a structured, completeness-checked brief.md for the first stage of a proposal pipeline.
Proposal Library Indexer
pawbytes/skill-suites
Turns case studies, past proposals and boilerplate dropped into a library inbox into structured, source-linked indexes for later proposal work.
Proposal Research Dossier Builder
pawbytes/skill-suites
Turns a structured sales brief into an evidence-backed HTML research dossier, matching indexed case studies locally and gathering client, tech-stack and pricing evidence from the web.
Related
Categories
Questions about Paw Tools Release
What does Paw Tools Release do?
Automates software releases from version bump to GitHub release. Paw Tools Release is an agent skill from pawbytes/skill-suites. Automates software releases from version bump to GitHub release.
When should I use Paw Tools Release?
Paw Tools Release fits situations like: the user requests to create a release; publish a new version; prepare a release.
How do I install Paw Tools Release in Claude Code?
Run `npx skills add pawbytes/skill-suites --skill paw-tools-release -a claude-code`. Or copy the skill folder (src/tools/paw-tools-release in pawbytes/skill-suites) into .claude/skills/paw-tools-release in your project. Claude Code loads it when a task matches its description.
How do I install Paw Tools Release in Codex?
Run `npx skills add pawbytes/skill-suites --skill paw-tools-release -a codex`. Or copy the skill folder (src/tools/paw-tools-release in pawbytes/skill-suites) into .agents/skills/paw-tools-release in your project. Codex loads it when a task matches its description.
Can I use Paw Tools Release in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pawbytes/skill-suites --skill paw-tools-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paw-tools-release, .gemini/skills/paw-tools-release, .github/skills/paw-tools-release and .opencode/skills/paw-tools-release in your project.
What does Paw Tools Release need to run?
Going by SKILL.md and its folder, Paw Tools Release needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Paw Tools Release access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Paw Tools Release safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Paw Tools Release use?
Paw Tools Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Paw Tools Release use?
About 782 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.
What are the alternatives to Paw Tools Release?
Skills that share tags, products or a category with Paw Tools Release: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Paw Tools Release?
pawbytes (a GitHub organization) maintains it in pawbytes/skill-suites, which has 110 GitHub stars. The repository holds 71 skills in this directory. The repository was last updated on October 3, 2026.
Source: pawbytes/skill-suites on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.