create-release-note

create-release-note is a command for coding agents from wangke19/gemini-ai-helpers. It costs 14 tokens per session (4,322 once invoked), scanned A, a copy of create-release-note, Apache-2.0.

A release-note generator that reads Jira bug tickets and linked GitHub pull requests, then writes a structured note back to Jira.

In plain words
What is it for?
Use it to create notes covering the cause, consequence, fix, result, and workaround for a bug. It also fills Jira's release-note fields.
Why use it?
It removes the need to gather details from Jira and GitHub and format each note by hand. It helps keep bug-fix notes consistent and complete.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/wangke19/gemini-ai-helpers/create-release-note
Clone the repo
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-release-note

README.md
[![agentmods](https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/create-release-note.svg)](https://agentmods.dev/commands/wangke19/gemini-ai-helpers/create-release-note)
Your own site
<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/create-release-note"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/create-release-note.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,322 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.04322
Opus 5 $0.00007 $0.02161
Sonnet 5 $0.00003 $0.00864
Haiku 4.5 $0.00001 $0.00432

Measured 2d ago against content hash 1c31974df8ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

create-release-note scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

94% identical to create-release-note — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

extensions/jira/commands/create-release-note.md · 565 lines

How it starts

The opening of the file, as written. The whole thing — 565 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Name

jira:create-release-note

Synopsis

/jira:create-release-note <issue-key>

Description

The jira:create-release-note command automatically generates bug fix release notes by analyzing Jira bug tickets and their linked GitHub pull requests, then updates the Jira ticket with the generated release note content.

This command is particularly useful for:

  • Creating consistent, well-formatted release notes across all bugs
  • Automatically extracting information from multiple sources (Jira + GitHub)
  • Saving time by analyzing PR code changes, commits, and descriptions
  • Ensuring complete release notes with Cause, Consequence, Fix, Result, and Workaround

The command follows the standard release note template format and populates both the Release Note Type and Release Note Text fields in Jira.

Implementation

The jira:create-release-note command runs in multiple phases:

🎯 Phase 1: Fetch and Validate Jira Bug

  1. Fetch bug ticket using mcp__atlassian__jira_get_issue MCP tool:

    • Request all fields to ensure we have complete data
    • Verify the issue is a Bug type
    • Extract issue description, links, and custom fields
  2. Validate issue type:

    • If not a Bug, warn user and ask if they want to continue
    • Release notes are typically for bugs, but may apply to other types
  3. Parse bug description to extract required sections:

    • Cause: The root cause of the problem
    • Consequence: The impact or effect of the problem
  4. Handle missing sections:

    • If Cause or Consequence sections are missing, inform the user
    • Provide template format and ask user to update the bug description
    • Optionally, allow user to provide Cause/Consequence interactively

🔗 Phase 2: Extract Linked GitHub PRs

Extract all linked GitHub PR URLs from multiple sources:

  1. Remote links (Primary source - web links in Jira):
    • Check the Jira issue response for web links/remote links
    • Common field names: remotelinks, issuelinks with outwardIssue.fields.issuetype.name == "GitHub PR"
    • Look for GitHub PR URLs in remote link objects
    • Pattern: https://github.com/{org}/{repo}/pull/{number}
    • Extract PR URLs and parse into {org}/{repo} and {number}

Read the full file on GitHub · 565 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 565 lines · 14 tokens per session scan A 1c31974df8ba

Subscribe to this mod's changes

create-release-note is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 4,322 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to create-release-note, differing in 25 lines, and is treated as a copy.