plugins/ci/skills/add-jira-triage-link/SKILL.md
Add a Component Readiness triage record link to a JIRA issue description
npx skillsauth add openshift-eng/ai-helpers add-jira-triage-linkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill adds a Component Readiness triage record link to a JIRA issue description so that anyone viewing the bug can monitor the on-going status of all regressions triaged to it.
Use this skill after creating or updating a triage record via the triage-regression skill. The link gives bug viewers a way to see all regressions associated with the bug in Component Readiness.
script_path="plugins/ci/skills/add-jira-triage-link/add_jira_triage_link.py"
python3 "$script_path" OCPBUGS-12345 \
--triage-id 456 \
--format json
Arguments:
issue_key: JIRA issue key (e.g., OCPBUGS-12345)Required Options:
--triage-id <id>: Triage record ID from Component ReadinessOptions:
--format json|text: Output format (default: text)output=$(python3 "$script_path" OCPBUGS-12345 --triage-id 456 --format json)
success=$(echo "$output" | jq -r '.success')
if [ "$success" = "true" ]; then
already=$(echo "$output" | jq -r '.already_present')
if [ "$already" = "true" ]; then
echo "Triage link already in description"
else
echo "Triage link added"
fi
fi
Success (link added):
{
"success": true,
"issue_key": "OCPBUGS-12345",
"triage_url": "https://sippy-auth.dptools.openshift.org/sippy-ng/component_readiness/triages/456",
"already_present": false
}
Success (link already present):
{
"success": true,
"issue_key": "OCPBUGS-12345",
"triage_url": "https://sippy-auth.dptools.openshift.org/sippy-ng/component_readiness/triages/456",
"already_present": true
}
Error:
{
"success": false,
"error": "Failed to update description: HTTP 403: ...",
"issue_key": "OCPBUGS-12345"
}
triage-regression (creates triage records that produce the triage ID)set-release-blocker (similar pattern for updating JIRA issue fields)/ci:analyze-regression (calls this skill after triaging)tools
Analyze a JIRA issue and create a pull request to solve it. Use when the user wants to implement a fix or feature described in a Jira issue, push a branch, and open a draft PR.
development
Use when a deeper level of code review is requested. Multi-agent panel code review with specialist reviewers and forced runtime reproducers for all BLOCKING bug findings. Optionally posts to GitHub/GitLab as a PENDING review.
development
Review agentic documentation — verify claims locally against source code first, then use chai-bot for cross-repo and cross-functional verification
development
Use this skill when debugging a failed Prow CI job.