generate-enhancement

generate-enhancement is a command for Claude Code from wangke19/gemini-ai-helpers. It costs 12 tokens per session (1,971 once invoked), scanned A, a copy of generate-enhancement, Apache-2.0.

A document generator that turns a Jira epic or feature into a Markdown OpenShift enhancement proposal. OpenShift is Red Hat's Kubernetes-based platform, and an enhancement proposal describes a planned platform change.

In plain words
What is it for?
Use it to start formal enhancement proposals from Jira planning records while incorporating linked epic details and the OpenShift template.
Why use it?
It removes repetitive copying from Jira into the required proposal structure. It also identifies missing information for later refinement.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

Good fit Use it to start formal enhancement proposals from Jira planning records while incorporating linked epic details and the OpenShift template.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/wangke19/gemini-ai-helpers/generate-enhancement
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.

Clone the repo
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers

Made for: Claude Code.

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 generate-enhancement

README.md
[![agentmods](https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/generate-enhancement/github.svg)](https://agentmods.dev/commands/wangke19/gemini-ai-helpers/generate-enhancement)
Your own site
<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/generate-enhancement"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/generate-enhancement/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for generate-enhancement

Your own site · 80×15
<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/generate-enhancement"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/generate-enhancement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,971 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 98% 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.00012 $0.01971
Opus 5 $0.00006 $0.00986
Sonnet 5 $0.00002 $0.00394
Haiku 4.5 $0.00001 $0.00197

Measured 6d ago against content hash c30035445a4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

generate-enhancement 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 6d 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

98% identical to generate-enhancement — 4 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/generate-enhancement.md · 270 lines

How it starts

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

Name

jira:generate-enhancement

Synopsis

/jira:generate-enhancement <issue-key>

Description

The jira:generate-enhancement command generates an OpenShift enhancement proposal markdown file based on a Jira epic or feature. It fetches the feature details, analyzes the content, and creates a properly formatted enhancement document following the OpenShift enhancement template structure.

This command is particularly useful for:

  • Converting strategic Jira features or epics into formal enhancement proposals
  • Bootstrapping enhancement documents with epic/feature context
  • Maintaining consistency between Jira planning and enhancement documentation
  • Accelerating the enhancement proposal writing process

Key Features

  • Automatic Feature Fetching - Retrieves feature details from Jira including description, epics, and context
  • Template-Based Generation - Creates enhancement markdown following the official OpenShift template
  • Content Mapping - Intelligently maps Jira feature fields to enhancement sections
  • Epic Integration - Incorporates linked epics as implementation details
  • Interactive Refinement - Prompts for missing information and clarifications
  • File Naming - Generates appropriate filename based on feature summary

Workflow

The command follows these steps:

1. Fetch Jira Epic or Feature

  • Retrieve epic/feature details using MCP Jira tools or REST API
  • Extract summary, description, child issues, components, timeline
  • Validate issue type (must be an Epic or Feature issue type)

2. Analyze Epic or Feature Content

  • Parse description, goals, acceptance criteria
  • Identify user stories and objectives
  • Extract scope and child issues (epics, stories, tasks)
  • Determine topology considerations from components

3. Generate Enhancement Sections

  • Map Jira content to enhancement template sections
  • Create initial draft with available information
  • Identify gaps requiring user input

4. Interactive Refinement

  • Prompt for technical implementation details
  • Collect test plan information
  • Define graduation criteria
  • Gather operational considerations

Read the full file on GitHub · 270 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. 6d ago First seen · 270 lines · 12 tokens per session scan A c30035445a4e

Subscribe to this mod's changes

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