A command that reads a Jira issue, examines the codebase, implements the requested fix, and creates a pull request. A pull request is a proposed code change submitted for review before merging.

It helps analyze Jira requirements, make the corresponding code changes, and open a pull request for the issue.

It connects a Jira problem report with the code changes needed to resolve it, reducing the work of starting the fix manually.

solve — Command for Claude Code by wangke19

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/solve/github.svg)](https://agentmods.dev/commands/wangke19/gemini-ai-helpers/solve)

Your own site

<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/solve"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/solve/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/solve"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/solve.svg" alt="Reviewed on agentmods" width="80" 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 2,096 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.02096
Opus 5	$0.00007	$0.01048
Sonnet 5	$0.00003	$0.00419
Haiku 4.5	$0.00001	$0.00210

Measured 9d ago against content hash 8bef36fb6aef, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

solve scanned grade A with 1 finding 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 9d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- The command uses curl to fetch JIRA data via REST API: https://redhat.atlassian.net/rest/api/3/issue/{$1}

extensions/jira/commands/solve.md · 147 lines

How it starts

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

Name

jira:solve

Synopsis

/jira:solve <jira-issue-id> [remote] [--ci]

Description

The jira:solve command analyzes a JIRA issue and creates a pull request to solve it.

This command takes a JIRA URL, fetches the issue description and requirements, analyzes the codebase to understand how to implement the solution, and creates a comprehensive pull request with the necessary changes.

Usage Examples:

Solve a specific JIRA issue:
```
/jira:solve OCPBUGS-12345 origin
```

Implementation

The command uses curl to fetch JIRA data via REST API: https://redhat.atlassian.net/rest/api/3/issue/{$1}
Parses JSON response using jq or text processing
Extracts key fields: summary, description, components, labels
Authentication uses Basic auth with JIRA_USERNAME and JIRA_API_TOKEN for Atlassian Cloud
Creates a PR with the solution

Process Flow

Issue Analysis: Parse JIRA URL and fetch issue details:
- Use curl to fetch JIRA issue data: curl -s -u "$JIRA_USERNAME:$JIRA_API_TOKEN" "https://redhat.atlassian.net/rest/api/3/issue/{$1}"
- Parse JSON response to extract:
  - Issue summary and description
  - From within the description expect the following sections
    - Required
      - Context
      - Acceptance criteria
    - Optional
      - Steps to reproduce (for bugs)
      - Expected vs actual behavior
- If --ci flag ($3) is NOT set: Ask the user for further issue grooming if the required sections are missing
- If --ci flag ($3) IS set: Proceed with available information, making reasonable assumptions where needed
Codebase Analysis: Search and analyze relevant code:
- Find related files and functions
- Understand current implementation
- Identify areas that need changes
- Use Grep and Glob tools to search for:
  - Related function names mentioned in JIRA
  - File patterns related to the component
  - Similar existing implementations
  - Test files that need updates

Read the full file on GitHub · 147 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.

9d ago First seen · 147 lines · 14 tokens per session scan A 8bef36fb6aef

Subscribe to this mod's changes

solve 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 2,096 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Git and workflow Project management extentions gemini-cli openshift redhat

wtfp:contribute

Guide a bounded WTF-P contribution from branch creation through a reviewable change request.

akougkas/wtf-p · 22 tokens

weekly-summary

Generate weekly work summary from git activity.

gopherguides/gopher-ai · 7 tokens

update-check.template

This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.

evan043/claude-cli-advanced-starter-pack · 0 tokens

cd-branch

Create a Conductor branch CARD and brief (does not open a session). Master only.

Jinghao67/conductor · 18 tokens

gh-issue

File a groomed, dispatchable GitHub issue from a breadcrumb (component/page/object) plus a problem description — recon the code, verify evidence, dedupe, label, file. Optionally pin the dispatch model/effort. Example — /gh-issue "Settings > Billing > Invoice row" clicking an invoice opens a 404 model:opus effort:high.

skyfox675/agents-skills · 74 tokens

feature-implement

Implement new feature from GitHub issue with full development workflow.

matteocervelli/llms · 11 tokens

solve