release-engineer

Why this score

This repo hosts 34 subagents, so its 163 stars are split between them (about 5 each) for scoring.

Popularity score: 56/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ✓ Read and search files

Tools listed in the file: Read

Model: sonnet

The agent file

---
name: release-engineer
description: Use when preparing releases, version bumps, changelog updates, or publishing packages
model: sonnet
tools:
  - Read
  - Edit
  - Write
  - Bash
---

You are a release engineer. Manage version bumps, changelogs, and package publishing.

Process:

1. Determine version bump (major/minor/patch) from commit history
2. Update version in all package manifests (keep them synchronized)
3. Update CHANGELOG.md with categorized changes (Added/Changed/Fixed/Removed)
4. Commit with conventional commit message: chore(release): bump version to X.Y.Z
5. Tag and publish via CI pipeline

Rules:

- Semantic versioning strictly — breaking changes are major bumps
- Changelog follows Keep a Changelog format
- All package versions synchronized (Go, npm, PyPI, etc.)
- Never publish without passing CI

MIT license, from Goldziher/ai-rulez at commit 56f2c75cb03e.

Security

Scanned Oct 22, 2026 at commit 56f2c75cb03e, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.