Skip to content
Back to skills

Paw Tools Release

ASecurity

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'.

  • 116 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 10, 2026
toolsgogit

Works with

  • cli

Security analysis

A100/100

Pro scans all 9 files and shows the line behind each finding

Scanned November 9, 2026

npx -y skills add pawbytes/skill-suites --skill paw-tools-release --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Paw Tools Release?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Paw Tools Release
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pawbytes-paw-tools-release/badge)](https://www.skillsdirectory.com/skills/pawbytes-paw-tools-release)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

## Resolution rules

- `{skill-root}` is this skill's folder; bare paths (`references/...`, `scripts/...`) resolve from it.
- `{suite-root}` is `root` from `uv run {skill-root}/scripts/paw-paths.py detect`, normally `{project-root}/paw-suites/tools`. All paths below are relative to it. A custom folder in config `tools.release_output_folder` wins (`detect` lists it under `overrides`; an old default is not one).
- When `detect` reports `mode: legacy` or `both`, the user's files are still partly in the old `.pawbytes/tools-output/` tree. Pass every path through `paw-paths.py locate <path>` (add `--write` for a new file) and use the path it returns. Once per session, tell the user that `paw-tools-setup` can move them to `paw-suites/tools/`, and offer it. Keep working either way.

## On Activation

Load available config from `{project-root}/.pawbytes/config/config.yaml` and `{project-root}/.pawbytes/config/config.user.yaml` (root keys and the `tools` section) if present. If config is missing, continue with sensible defaults.

Extract relevant config keys:
- `tools.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:

1. **Git repository** — Must be in a git repository with at least one commit
2. **GitHub CLI** — `gh` must be installed and authenticated for GitHub releases
3. **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:

1. **Validate** → `./references/01-validate.md`
2. **Version** → `./references/02-version.md`
3. **Changelog** → `./references/03-changelog.md`
4. **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/alpha` flag 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 | `{suite-root}/releases/YYYY-MM-DD-v{version}.md` |

## 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.

Files in this skill

  • SKILL.md3.1 KB
  • references/01-validate.md1.4 KB
  • references/02-version.md1.9 KB
  • references/03-changelog.md2.3 KB
  • references/04-release.md2.8 KB
  • scripts/detect_version_files.py5.8 KB
  • scripts/parse_commits.py7.8 KB
  • scripts/tests/test_detect_version_files.py3.1 KB
  • scripts/tests/test_parse_commits.py5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in tools →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.