Skip to content
Back to skills

Release

BSecurity

Prepare and publish a new agents-farm release (version bump, changelog, tag, GitHub release). Use only when the user asks for a release.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentspythonbashgitapisecurity

Works with

  • api

Security analysis

B75/100
  • criticalDownloads and executes remote scripts — classic supply chain attack

Pro shows the line behind each finding and how to fix it

Scanned November 18, 2026

npx -y skills add mythes/agents-farm --skill release --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Release?

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

Security grade badge for Release
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/mythes-release/badge)](https://www.skillsdirectory.com/skills/mythes-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: release
description: Prepare and publish a new agents-farm release (version bump, changelog, tag, GitHub release). Use only when the user asks for a release.
disable-model-invocation: true
---

# Release

A release is public and cannot be undone cleanly. **Ask the user to confirm before you push, tag or publish.** Show what you will do first.

## Before you start

1. The working tree must be clean (`git status --short` is empty) and you are on `main`.
2. `git pull --ff-only` works, and the last CI run on `main` is green: `gh run list --branch main --limit 1`.
3. Run the `check` skill. All checks must pass.
4. Ask the user for the new version (semantic versioning: `0.x.y` while the API is not stable). Suggest one from the commits since the last tag (`git log <last-tag>..HEAD --oneline`).

## Steps

1. Update the version in **both** places: `pyproject.toml` (`version = "…"`) and `agents_farm/__init__.py` (`__version__`). A test checks they are equal.
2. Update `CHANGELOG.md` (create it if it does not exist). Use the sections **Added / Changed / Fixed / Security**, write plain English, one short line per change, and link issues like `#12`.
3. Run the `check` skill again.
4. Commit: `Release vX.Y.Z`.
5. **Ask for confirmation.** Then:

   ```bash
   git tag -a vX.Y.Z -m "vX.Y.Z"
   git push origin main --follow-tags
   gh release create vX.Y.Z --title "vX.Y.Z" --notes-file <notes>
   ```

   Use the changelog section of this version as the notes. Do not attach big files.
6. Check that the release page and the CI run are fine. Tell the user the release URL.
7. **Update the Homebrew formula** in the separate repository `mythes/homebrew-tap` (`Formula/agents-farm.rb`): set the new tag in `url`, and the new `sha256` (`curl -sL <url> | shasum -a 256`). If the dependencies changed, refresh the `resource` blocks (`brew update-python-resources mythes/tap/agents-farm`). Test with `brew reinstall mythes/tap/agents-farm`, `brew test` and `brew audit --strict --online`. Then ask the user before you push the tap.

## Rules

- Never force-push and never move or delete an existing tag.
- The repository may be private. Do not change its visibility inside this skill.
- If a step fails, stop and report the real error. Do not retry with other flags to get around a check.

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 ai-agents →

Comments

Loading comments…

Newsletter

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