agentmods.dev

check-if-jira-regression-is-ongoing

check-if-jira-regression-is-ongoing is a command for Claude Code from openshift-eng/ai-helpers. It costs 15 tokens per session (3,496 once invoked), scanned A, original, Apache-2.0.

A command that checks whether a regression recorded in a Jira bug is still failing. Jira is a system for tracking bugs and development work; Sippy and Component Readiness provide live test and regression data.

In plain words
What is it for?
It accepts a Jira issue key or URL, reads the bug and its comments, extracts test and regression identifiers, and compares them with current data from Sippy and Component Readiness.
Why use it?
It helps determine whether a bug can be closed, whether a fix is working, or whether newer failures appeared for the same test. It also finds related triaged bugs that may cover the same problem.

Command for Claude Code

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

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is release=$(python3 plugins/ci/skills/fetch-releases/fetch_releases.py --latest).

Part of the ci plugin — 34 skills, 21 commands, 2 agents shipped together

not rated 116repo today A scan 15 tokens original Apache-2.0

Good fit It accepts a Jira issue key or URL, reads the bug and its comments, extracts test and regression identifiers, and compares them with current data from Sippy and Component Readiness.

Compare 6 commands from other repositories ↓
View source ↗ openshift-eng/ai-helpers openshift-eng.github.io
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/openshift-eng/ai-helpers
agentmods
npx agentmods add commands/openshift-eng/ai-helpers/check-if-jira-regression-is-ongoing

Made for: Claude Code.

Or install ci, the plugin that ships this one along with the rest of its 34 skills, 21 commands, 2 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/check-if-jira-regression-is-ongoing/github.svg)](https://agentmods.dev/commands/openshift-eng/ai-helpers/check-if-jira-regression-is-ongoing)
Your own site
<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/check-if-jira-regression-is-ongoing"><img src="https://agentmods.dev/badge/commands/openshift-eng/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.

agentmods 80×15 button for check-if-jira-regression-is-ongoing

Your own site · 80×15
<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/check-if-jira-regression-is-ongoing"><img src="https://agentmods.dev/badge/commands/openshift-eng/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 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.

ModelPer sessionOnce 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 2387545d99c5, 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

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/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

  1. 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/||')

  2. Fetch Jira Issue: Read the bug description, status, and comments

    Use the fetch-jira-issue skill to retrieve the bug data:

    jira_script="plugins/ci/skills/fetch-jira-issue/fetch_jira_issue.py"
jira_data=$(python3 "$jira_script" "$jira_key" --format json)

    See plugins/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)

  3. 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.

  1. 11d ago First seen · 337 lines · 15 tokens per session scan A 2387545d99c5

Subscribe to this mod's changes

check-if-jira-regression-is-ongoing is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging
Related

Other commands, from other repositories

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

fix

Universal debugging and fix application with semantic code analysis.

stefan-jansen/claude-code-toolkit · 9 tokens

doctor

Badi configuration validation. Checks all Badi components and produces a diagnostic report.

fatihkan/badi · 0 tokens

http-service

Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.

MadAppGang/magus · 27 tokens

gh-issue-use-cypress

Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.

skyfox675/agents-skills · 49 tokens