From ci
Add a Component Readiness triage record link to a JIRA issue description so viewers can monitor regressions triaged to the bug.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ci:add-jira-triage-linkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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)npx claudepluginhub jluhrsen/ai-helpers --plugin ciAdd a Component Readiness triage record link to a JIRA issue description so viewers can monitor regressions triaged to the bug.
Create/remove/inspect JIRA issue-to-issue links (blocks, depends on, clones, relates to) via jira-as wrapper. Supports triggers like 'link KEY blocks KEY', 'what blocks KEY', 'clone KEY'. Not for sprint/epic.