Agent skill

Managing Python Releases

Manages Python library releases including semantic versioning, changelog maintenance (Keep a Changelog format), release automation with GitHub Actions, and deprecation workflows.

MITAuto-check passedDevelopment

Install Managing Python Releases

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill managing-python-releases -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill managing-python-releases --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-management .claude/skills/managing-python-releases && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "managing-python-releases" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/release-management into .claude/skills/managing-python-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-python-releases", 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

$skill-installer install https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/release-management

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

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill managing-python-releases -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill managing-python-releases --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release-management .agents/skills/managing-python-releases && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "managing-python-releases" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/release-management into .agents/skills/managing-python-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-python-releases", 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.

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill managing-python-releases -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill managing-python-releases --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release-management .cursor/skills/managing-python-releases && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "managing-python-releases" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/release-management into .cursor/skills/managing-python-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-python-releases", 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

$ gemini skills install https://github.com/kajisho5/ffmpeg-skill.git --path .claude/skills/release-management

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill managing-python-releases -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill managing-python-releases --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release-management .gemini/skills/managing-python-releases && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "managing-python-releases" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/release-management into .gemini/skills/managing-python-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-python-releases", 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.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill managing-python-releases

Installs 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).

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill managing-python-releases -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release-management .github/skills/managing-python-releases && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "managing-python-releases" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/release-management into .github/skills/managing-python-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-python-releases", 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.

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill managing-python-releases -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill managing-python-releases --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release-management .opencode/skills/managing-python-releases && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "managing-python-releases" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/release-management into .opencode/skills/managing-python-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-python-releases", 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: managing-python-releases
GitHub stars: 1.9k
Token cost: ~1.1k tokens
SKILL.md length: 228 words
Files: 1
Skills in repo: 14
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Manages Python library releases including semantic versioning, changelog maintenance (Keep a Changelog format), release automation with GitHub Actions, and deprecation workflows.

Planning releases
SKILL.md covers Semantic Versioning, Changelog Format (Keep a…, Version in Code and GitHub Actions Release (PyPI…, plus 4 more sections
Calls git and npm; reaches github.com
Writing changelogs

What it does

Managing Python Releases is an agent skill from kajisho5/ffmpeg-skill. Manages Python library releases including semantic versioning, changelog maintenance (Keep a Changelog format), release automation with GitHub Actions, and deprecation workflows. Use when planning releases, writing changelogs, automating release pipelines, or communicating breaking changes.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes, CI/CD and Open source maintenance. It works with Python, GitHub Actions and npm. The licence is MIT.

When your agent uses it

Planning releases
Writing changelogs
Automating release pipelines
Communicating breaking changes

Example prompts

“Use the managing-python-releases skill to manage Python library releases including semantic versioning, changelog maintenance (Keep a Changelog…”
“/managing-python-releases”

Requirements

Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 008333a. 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
Shell commands in SKILL.md call:
- git
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
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

Managing Python Releases loads about 1.1k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 228 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~79
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from kajisho5/ffmpeg-skill at commit 008333a, republished under its MIT licence (© kajisho5). 228 words, ~1,061 tokens.

Download SKILL.mdSave it as .claude/skills/managing-python-releases/SKILL.md (or your agent's skills folder).

name: managing-python-releases
description: Manages Python library releases including semantic versioning, changelog maintenance (Keep a Changelog format), release automation with GitHub Actions, and deprecation workflows. Use when planning releases, writing changelogs, automating release pipelines, or communicating breaking changes.

Release Management

Semantic Versioning

MAJOR.MINOR.PATCH (e.g., 1.2.3)

PATCH: Bug fixes, no API changes
MINOR: New features, backward compatible
MAJOR: Breaking changes

Changelog Format (Keep a Changelog)

markdown

# Changelog

## [Unreleased]
### Added
- New `batch_encode()` function

## [1.2.0] - 2024-03-15
### Added
- Support for custom formats (#123)

### Fixed
- Edge case at -180 longitude (#145)

### Deprecated
- `old_function()` - use `new_function()` instead

[Unreleased]: https://github.com/user/repo/compare/v1.2.0...HEAD
[1.2.0]: https://github.com/user/repo/releases/tag/v1.2.0

Categories: Added, Changed, Deprecated, Removed, Fixed, Security

Version in Code

python

# src/package/__init__.py
__version__ = "1.2.3"

# Or use importlib.metadata
from importlib.metadata import version
__version__ = version("my-package")

GitHub Actions Release (PyPI example)

A tag-triggered workflow builds and publishes to a registry via trusted publishing (no stored token) is the general shape — swap the publish step for whatever registry the project actually uses (PyPI, npm, crates.io, ...):

yaml

# .github/workflows/release.yml
on:
  push:
    tags: ['v*']

jobs:
  release:
    runs-on: ubuntu-latest
    permissions:
      contents: write      # create the GitHub release
      id-token: write      # trusted publishing (no token)
    steps:
      - uses: actions/checkout@v4
      - uses: astral-sh/setup-uv@v5
      - run: uv build
      - uses: softprops/action-gh-release@v2
        with:
          files: dist/*
      - uses: pypa/gh-action-pypi-publish@release/v1

Deprecation Process

Warn with stacklevel=2 so the message points at the caller.

python

import warnings

def old_function():
    """Deprecated: Use new_function() instead."""
    warnings.warn(
        "old_function() deprecated, will be removed in 2.0.0",
        DeprecationWarning,
        stacklevel=2,
    )
    return new_function()

Release Process

bash

# 1. Update CHANGELOG.md (move Unreleased to version)
# 2. Bump version in the project manifest
# 3. Commit and tag
git commit -am "Release v1.2.0"
git tag -a v1.2.0 -m "Release v1.2.0"
git push origin main --tags
# 4. CI publishes automatically (if automated) or publish manually

Checklist

Before Release:
- [ ] All tests pass
- [ ] CHANGELOG updated
- [ ] Version bumped
- [ ] Documentation current

After Release:
- [ ] Registry shows new version
- [ ] A fresh install actually works (not just that the tag/publish succeeded)
- [ ] GitHub release created
- [ ] Docs updated

Note for this repository (ffmpeg-skill)

CHANGELOG.md here already follows Keep a Changelog's dated-section format (## 0.10.0 — 2026-09-06 — ...), so the format guidance above matches this repo exactly. Two real differences from the generic PyPI example:

No automated release workflow exists. There is no .github/workflows/release.yml — the 0.10.0 release this session did every step by hand: bump package.json's version, convert the CHANGELOG's ## Unreleased into a dated section, git tag, create the GitHub Release, then npm publish separately. This is exactly the gap managing-python-releases is meant to close with automation — worth considering if releases become frequent enough that a manual miss (like 0.9.2 sitting un-published to npm for a while, discovered this session) becomes a recurring problem.
The registry is npm, not PyPI, and there is no __version__ in code — scripts/_contract.py's skill_version() and doctor's version field both read package.json directly (see this repo's own concurrent-branches and build-artifacts skill notes for the related merge-conflict and publish-verification patterns this touches).

Source: wdm0006/python-skills (MIT).

Files

Just SKILL.md in .claude/skills/release-management of kajisho5/ffmpeg-skill.

Open the folder on GitHubat commit 008333a

Compare with similar skills

Managing Python Releases 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.

Managing Python Releases compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Managing Python Releases this skillkajisho5/ffmpeg-skill	1.9k	—	~1.1k	Automated safety check: Pass	MIT	2 days ago
Ccb GitHubSeemSeam/claude_codex_bridge	3.5k	—	~4.9k	Automated safety check: Pass	Custom licence	yesterday
Cline CLI Release Publishercline/cline	70k	—	~3.4k	Automated safety check: Warn	Apache-2.0	today
Automate npm Releasejd-solanki/slidev-theme-dracula	161	—	~626	Automated safety check: Pass	None	3 mo ago
Code Reviewoaslananka/kicad-mcp-pro	119	—	~3.9k	Automated safety check: Pass	MIT	today
MCP Server Trello Releasedelorenj/mcp-server-trello	446	—	~3.5k	Automated safety check: Pass	MIT	13 days ago

Similar skills

Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
3.5k GitHub stars~4.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Cline CLI Release Publisher
cline/cline
Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.
70k GitHub stars~3.4k tokensUpdated today
DevelopmentAuto-check: warnings
Automate npm Release
jd-solanki/slidev-theme-dracula
Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and…
161 GitHub stars~626 tokensUpdated 3 mo ago
DevelopmentAuto-check passed
Code Review
oaslananka/kicad-mcp-pro
A skill your agent uses for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro.
119 GitHub stars~3.9k tokensUpdated today
DevelopmentAuto-check passed
MCP Server Trello Release
delorenj/mcp-server-trello
Canonical build → release → tag → publish procedure for the @delorenj/mcp-server-trello repo.
446 GitHub stars~3.5k tokensUpdated 13 days ago
DevelopmentAuto-check passed
Release Coherence
macalbert/envilder
Unified release coherence workflow for any component (CLI, GHA, or SDK).
138 GitHub stars~1.3k tokensUpdated 2 days ago
DevelopmentAuto-check passed

More from kajisho5/ffmpeg-skill

All 14 skills in this repo

Ffmpeg Skill
kajisho5/ffmpeg-skill
Edit video and audio with local FFmpeg from natural-language requests: cut, trim, join, resize/reframe (9:16, 1:1), speed change, captions and subtitles (SRT/ASS, animated, karaoke), logos and text…
1.9k GitHub stars~7.4k tokensUpdated 2 days ago
Auto-check passed
CI Pipeline Synthesizer
kajisho5/ffmpeg-skill
Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.
1.9k GitHub starsUsed in 1 repo~1.1k tokens
Auto-check passed
Reviewing Ffmpeg Skill Changes
kajisho5/ffmpeg-skill
Review a change to the ffmpeg-skill repository for the failures its own contract makes possible — a claim in a result document that is true at one layer and false at the layer a caller reads, a new…
1.9k GitHub stars~2.3k tokensUpdated 2 days ago
Auto-check passed
Building Python MCP Servers
kajisho5/ffmpeg-skill
Builds robust Python MCP (Model Context Protocol) servers with FastMCP — tool design, error contracts, event-loop-safe blocking work, subprocess/CLI wrapping, single-file vs packaged distribution…
1.9k GitHub stars~3.2k tokensUpdated 2 days ago
Auto-check passed
Concurrent Branches
kajisho5/ffmpeg-skill
Resolve conflicts and merges when several branches are open against one repo at the same time — the hotspot files every change must touch (registry manifests, a single version field, shared tool…
1.9k GitHub stars~2.8k tokensUpdated 2 days ago
Auto-check passed
Guarding Destructive Operations
kajisho5/ffmpeg-skill
Add and review preconditions on operations that delete, overwrite, rewrite history, or resolve a caller-supplied name to a filesystem path — refusing instead of warning, placing the guard ahead of…
1.9k GitHub stars~2.6k tokensUpdated 2 days ago
Auto-check passed

Works with

Questions about Managing Python Releases

What does Managing Python Releases do?

Manages Python library releases including semantic versioning, changelog maintenance (Keep a Changelog format), release automation with GitHub Actions, and deprecation workflows. Managing Python Releases is an agent skill from kajisho5/ffmpeg-skill. Manages Python library releases including semantic versioning, changelog maintenance (Keep a Changelog format), release automation with GitHub Actions, and deprecation workflows.

When should I use Managing Python Releases?

Managing Python Releases fits situations like: planning releases; writing changelogs; automating release pipelines; communicating breaking changes.

How do I install Managing Python Releases in Claude Code?

Run `npx skills add kajisho5/ffmpeg-skill --skill managing-python-releases -a claude-code`. Or copy the skill folder (.claude/skills/release-management in kajisho5/ffmpeg-skill) into .claude/skills/managing-python-releases in your project. Claude Code loads it when a task matches its description.

How do I install Managing Python Releases in Codex?

Run `npx skills add kajisho5/ffmpeg-skill --skill managing-python-releases -a codex`. Or copy the skill folder (.claude/skills/release-management in kajisho5/ffmpeg-skill) into .agents/skills/managing-python-releases in your project. Codex loads it when a task matches its description.

Can I use Managing Python Releases 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 kajisho5/ffmpeg-skill --skill managing-python-releases -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-python-releases, .gemini/skills/managing-python-releases, .github/skills/managing-python-releases and .opencode/skills/managing-python-releases in your project.

What does Managing Python Releases need to run?

Going by SKILL.md and its folder, Managing Python Releases needs the command-line tools its instructions call (git and npm). Our summary lists: Python 3.

Does Managing Python Releases access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Managing Python Releases 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. Review the folder before installing.

What licence does Managing Python Releases use?

Managing Python Releases 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 Managing Python Releases use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Managing Python Releases?

Skills that share tags, products or a category with Managing Python Releases: Ccb GitHub (SeemSeam/claude_codex_bridge, 3.5k stars), Cline CLI Release Publisher (cline/cline, 70k stars), Automate npm Release (jd-solanki/slidev-theme-dracula, 161 stars) and Code Review (oaslananka/kicad-mcp-pro, 119 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Managing Python Releases?

kajisho5 (a GitHub user) maintains it in kajisho5/ffmpeg-skill, which has 1,879 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 5, 2026.

Source: kajisho5/ffmpeg-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Managing Python Releases

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Release Management

Semantic Versioning

Changelog Format (Keep a Changelog)

Version in Code

GitHub Actions Release (PyPI example)

Deprecation Process

Release Process

Checklist

Note for this repository (ffmpeg-skill)

Files

Compare with similar skills

Similar skills

More from kajisho5/ffmpeg-skill

Related

Questions about Managing Python Releases