plugins/ci/skills/set-release-blocker/SKILL.md
Set the Release Blocker field on a JIRA issue
npx skillsauth add openshift-eng/ai-helpers set-release-blockerInstall 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.
Sets the "Release Blocker" custom field on a JIRA issue. Component Readiness regressions are treated as release blockers, so any bug filed for a regression should have this field set to "Approved".
See the release blocker definition for details on the criteria and process.
# Set Release Blocker to Approved (default)
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523
# Explicitly set to Approved
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523 --value Approved
# Set to Proposed
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523 --value Proposed
# Set to Rejected
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523 --value Rejected
# Clear the field
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523 --value ""
# JSON output
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523 --format json
customfield_10847Approved (option ID: 16772)Proposed (option ID: 16773)Rejected (option ID: 16774)Release Blocker set to 'Approved' on OCPBUGS-76523
https://redhat.atlassian.net/browse/OCPBUGS-76523
{
"success": true,
"issue_key": "OCPBUGS-76523",
"value": "Approved",
"url": "https://redhat.atlassian.net/browse/OCPBUGS-76523"
}
JIRA_API_TOKEN or JIRA_USERNAME is not set, the script exits with an error messagesuccess: false with the HTTP error detailstools
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.