What is check-if-jira-regression-is-ongoing?

A command that checks whether a regression described in a Jira bug is still failing. A regression is a problem where something that previously worked starts failing after a change; the command compares Jira details with live test data from Sippy and Component Readiness.

Use it with a Jira key or URL to check whether a fix works, whether new failures appeared, and whether related bugs exist.

It removes the need to manually compare an old bug report with current test results before deciding whether the bug is still active.

check-if-jira-regression-is-ongoing — Command for Claude Code by wangk

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

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

agentmods

npx agentmods add commands/wangke19/gemini-ai-helpers/check-if-jira-regression-is-ongoing

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/check-if-jira-regression-is-ongoing/github.svg)](https://agentmods.dev/commands/wangke19/gemini-ai-helpers/check-if-jira-regression-is-ongoing)

Your own site

<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/check-if-jira-regression-is-ongoing"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/check-if-jira-regression-is-ongoing/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/check-if-jira-regression-is-ongoing"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/check-if-jira-regression-is-ongoing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,496 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 100% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.03496
Opus 5	$0.00008	$0.01748
Sonnet 5	$0.00003	$0.00699
Haiku 4.5	$0.00002	$0.00350

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

Security

Grade A, and why

check-if-jira-regression-is-ongoing 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 11d 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.

curl -s -X POST \

Origin

This is a copy

100% identical to check-if-jira-regression-is-ongoing — 26 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/ci/commands/check-if-jira-regression-is-ongoing.md · 337 lines

How it starts

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

Name

ci:check-if-jira-regression-is-ongoing

Synopsis

/ci:check-if-jira-regression-is-ongoing <jira-key-or-url>

Description

The ci:check-if-jira-regression-is-ongoing command reads a Jira bug and determines whether the regression(s) it describes are still actively failing or have resolved. It extracts test names, test IDs, and regression IDs from the bug description, status, and comments, then cross-references with live data from Sippy and Component Readiness.

This command is useful for:

Checking if a bug's regression has resolved and the bug can be closed
Finding out if new regressions have appeared for the same test since the bug was filed
Discovering if other triaged bugs exist for the same test that don't match this bug
Getting a quick status on whether a fix has landed and is effective

Implementation

Parse Arguments: Extract the Jira key

Accept either a full URL or a bare key:
- https://redhat.atlassian.net/browse/OCPBUGS-74690 → OCPBUGS-74690
- OCPBUGS-74690 → OCPBUGS-74690
Strip the URL prefix if present:
```
jira_key=$(echo "$input" | sed 's|.*/browse/||')
```
Fetch Jira Issue: Read the bug description, status, and comments

Use the fetch-jira-issue skill to retrieve the bug data:
```
jira_script="extensions/ci/skills/fetch-jira-issue/fetch_jira_issue.py"
jira_data=$(python3 "$jira_script" "$jira_key" --format json)
```
See extensions/ci/skills/fetch-jira-issue/SKILL.md for complete implementation details including error handling.

Extract and read from the JSON output:
- summary: Bug title
- comments[].body: All comment bodies
- status: Current Jira status (e.g., New, Assigned, Modified, Closed)
- components[]: Jira component(s)
- progress.level: Automatic progress classification (ACTIVE/STALLED/NEEDS_ATTENTION/RESOLVED)
Extract Test Identifiers: Scan the bug for test names, test IDs, and regression IDs

Search through the summary, description, and all comment bodies for:

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

11d ago First seen · 337 lines · 15 tokens per session scan A 67c8a9c5fe50

Subscribe to this mod's changes

check-if-jira-regression-is-ongoing is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 3,496 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to check-if-jira-regression-is-ongoing, differing in 26 lines, and is treated as a copy.

Debugging extentions gemini-cli openshift redhat

audit

Run a structured codebase audit. Maps the architecture, assesses health (compliance, tests, docs), performs deep analysis (security, performance, code quality), and synthesizes a prioritized roadmap. Outputs land under docs/audit/ in this project. Phases 0-3 with human checkpoints between each phase. Use /audit-quick…

telus-labs/stagecraft · 78 tokens

check-if-jira-regression-is-ongoing