Skip to main content
Agent skill

Tag New Release

Create a new annotated git tag with release notes extracted from changelog files. Supports both macOS and Windows TinyClips release flows.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Tag New Release when an AI agent needs a reusable SKILL.md workflow for this job: Create a new annotated git tag with release notes extracted from changelog files. Supports both macOS and Windows TinyClips release flows.

When not to use it

Skip Tag New Release when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/tag-new-release
# Save SKILL.md to ~/.claude/skills/tag-new-release/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/tag-new-release/SKILL.md. For a shared project, commit the folder at .claude/skills/tag-new-release/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Tag New Release skill for this task: When preparing a new TinyClips release tag for macOS or Windows. Confirm any required inputs or files before making changes.

What supports this recommendation?

81/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
89/100
Practical detail
92/100
Source evidence
60/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Tag New Release

Create a new annotated git tag for a release based on the project's platform changelog.

## When to use

- When preparing a new TinyClips release tag for macOS or Windows. - When the user asks to tag a release. - When the user provides a version to tag, such as `v1.5.0-mac` or `v1.0.9-windows`. - When the user wants release notes extracted from the relevant changelog and included in the tag message.

## How to use

Request the release tag in chat (platform is required):

```text /tag-new-release --platform mac --version v1.5.0-mac ```

Or run the script directly from the repository root:

```bash bash .github/skills/tag-new-release/tag-new-release.sh --platform mac --version v1.5.0-mac ```

On Windows, use PowerShell:

```powershell powershell -ExecutionPolicy Bypass -File .github/skills/tag-new-release/tag-new-release.ps1 -Platform windows -Version v1.0.9-windows ```

If `--version` is provided, that exact tag value is used for the release. If `--version` is omitted: - macOS defaults to `v<Info.plist CFBundleShortVersionString>.0-mac` (for example, `v1.5.0-mac`) - Windows defaults to incrementing patch from the latest `v*-windows` tag.

## Step-by-step procedure

When asked to tag a new release:

1. **Check existing tags** - Inspect recent git tags for the selected platform. 2. **Determine release version**: - macOS: If the user provides a tag version, use it as the source of truth; otherwise validate it against `mac/TinyClips/Info.plist` `CFBundleShortVersionString` - Windows: Use provided tag or infer by incrementing the latest `-windows` patch tag 3. **Read platform changelog**: - macOS: root `CHANGELOG.md` - Windows: `windows/CHANGELOG.md` 4. **Update changelog** - Insert the release heading with today's date below Unreleased. 5. **Verify the working directory** - Ensure there are no uncommitted changes before creating commit/tag. 6. **Create commit** - Commit the changelog release marker. 7. **Create an annotated git tag** with: - A tag name matching the platform version (for example `v1.5.0-mac`, `v1.0.9-windows`) - A tag message containing the version and formatted release notes from the platform changelog 8. **Confirm the tag** - Show the created tag details to verify the tag name and message. 9. **Suggest pushing the tag** - Tell the user they can push with:

```bash git push origin <tag-name> ```

Do not push the tag unless the user explicitly asks.

## Release notes format

The tag message should include cleanly formatted release notes from the selected changelog entry for the release. Include all relevant sections, such as:

- Added - Improved - Fixed - Changed - Deprecated - Removed - Security

## Safety checks

- Do not create a release tag from a dirty working directory. - Do not overwrite an existing tag. - Do not push tags without explicit user approval. - If the requested version conflicts with existing tags, stop and ask the user how to proceed. - When the version is provided explicitly by the user, honor that value even if it differs from the app's current `Info.plist` version.

## Files included

- `tag-new-release.sh` - Script that automates changelog release marking, commit creation, and annotated tagging for macOS or Windows. - `tag-new-release.ps1` - PowerShell equivalent for running the same release-tag workflow natively on Windows.

Intended uses

  • When preparing a new TinyClips release tag for macOS or Windows.
  • When the user asks to tag a release.
  • When the user provides a version to tag, such as v1.5.0-mac or v1.0.9-windows.
  • When the user wants release notes extracted from the relevant changelog and included in the tag message.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.