Menu
Generates structured release notes from git commit history, PR titles, and linked issues. Supports Conventional Commits and custom formats.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
An autonomous code-assistant agent that can review code, answer technical questions, generate tests, and suggest refactors — powered by AgentVerse skills and an empathetic developer soul. Exposes MCP tools and is A2A (Agent-to-Agent) compatible.
Publish, discover, and manage AI skills, agents, workflows, souls and prompts from the AgentVerse marketplace. Use when working with the agentverse CLI to search/publish artifacts, authenticate, or manage AI agent ecosystem components.
Runs a suite of smoke tests against any REST API and reports status, latency, and failure details.
Reviews a pull request or diff and produces structured feedback on correctness, security, performance, and style.
Manage multi-container Docker environments using docker compose. Start, stop, inspect, and health-check services defined in a compose file — ideal for local dev, CI service orchestration, and integration test setup.
Fetch GitHub Pull Request diffs, metadata, and CI status using the gh CLI. Summarise changes, check review status, and post structured review comments.
| name | release-notes-writer |
| kind | skill |
| description | Generates structured release notes from git commit history, PR titles, and linked issues. Supports Conventional Commits and custom formats. |
| tags | ["release","ci","documentation","changelog"] |
| version | 0.1.0 |
| author | agentverse-ci |
| license | MIT |
Automatically generates well-formatted release notes from commit history, pull request metadata, and issue trackers — ready for GitHub Releases, CHANGELOG.md, or Slack notifications.
git tag push to auto-generate and post GitHub Release notesCHANGELOG.md that follows Keep a Changelog conventions{
"repo": "org/repo",
"from_ref": "v1.2.0",
"to_ref": "v1.3.0",
"format": "markdown",
"sections": ["breaking", "features", "fixes", "deps", "chores"],
"include_authors": true,
"issue_tracker": "github"
}
| Field | Required | Description |
|---|---|---|
repo | ✓ | GitHub owner/repo slug |
from_ref | ✓ | Start tag, branch, or commit SHA |
to_ref | ✗ | End ref (defaults to HEAD) |
format | ✗ | markdown (default), json, slack |
sections | ✗ | Which categories to emit |
include_authors | ✗ | Attribute changes to PR authors |
issue_tracker | ✗ | github or jira for issue link resolution |
| Prefix | Section |
|---|---|
feat: / feat!: | Features / Breaking Changes |
fix: | Bug Fixes |
deps: / chore: | Maintenance |
docs: | Documentation |
perf: | Performance |
## What's Changed in v1.3.0
### 🚀 Features
- Add skill import from GitHub repository URL (#142) @loonghao
- Support `github_repo` source type for directory-based skills (#138) @loonghao
### 🐛 Bug Fixes
- Fix `SourceType::GitHub` serialised as `git_hub` instead of `github` (#145)
### 📦 Dependencies
- Bump `zip` to 2.4.2
- Bump `axum` to 0.8.8
**Full Changelog**: https://github.com/org/repo/compare/v1.2.0...v1.3.0
on:
push:
tags: ['v*']
jobs:
release:
steps:
- name: Generate Release Notes
uses: agentverse/run-skill@v1
with:
skill: agentverse-ci/release-notes-writer
inputs: |
repo: ${{ github.repository }}
from_ref: ${{ github.event.before }}
to_ref: ${{ github.ref_name }}
format: markdown
env:
AGENTVERSE_TOKEN: ${{ secrets.AGENTVERSE_TOKEN }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Create GitHub Release
uses: softprops/action-gh-release@v2
with:
body: ${{ steps.generate.outputs.notes }}
! suffix or BREAKING CHANGE: footer) are always promoted to a dedicated section regardless of sections config.JIRA_BASE_URL and JIRA_TOKEN as environment variables.