Menu
Triage CCX rule release pipeline failures — identifies failed stage/job, classifies root cause, and suggests a fix.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
ObsInt Processing team reference — repos, services, deployment, clusters, shared coding standards, PR rules, and language conventions. Shared guidance for team repositories; repo-specific details live in each repo's AGENTS.md.
Generate a report of what you have worked on in a given quarter. The Quarterly Connection is something all Red Hat users must complete after a quarter has ended. There you talk what you have accomplished, the goals you had and the goals you want to set up for the next quarter. Most of this information is already in Jira, so we can use that to generate the report and help the user remember what they have done in those months. This should be used when the user asks for help writing the quarterly connection on Workday.
Collect GitHub PRs and GitLab MRs authored by a user during a given quarter. Produces a themed report of code contributions across team repositories. Use alongside the quarterly-connection-jiras skill to complement Jira-based reports with actual code work, or standalone when the user asks for a PR/MR summary.
Triage Glitchtip-sourced Jira tickets in the CCXDEV project — detect duplicates, investigate root causes via stack traces and source code, and post "[AI suggestion]" comments. Use this skill whenever the user mentions triaging Glitchtip errors, reviewing ccx-processing/obsint-processing Jira tickets, deduplicating error reports, or investigating production/staging errors tracked in Jira with the glitchtip label.
Generate the weekly Processing team Scrum of Scrums report from Jira epics. Compares progress over the last 7 days (report day is usually Wednesday): child-task movement, epic completion %, and epic status updates. Use when the user asks for a scrum of scrums, SoS report, weekly epic status, processing epic report, or Wednesday status report.
Triage CCX Jenkins CI failures — classifies failure patterns (isolated blip, consecutive, flapping), analyzes logs, matches against known issues, and recommends action. Covers all active CCX jobs.
| name | triage-rule-release |
| description | Triage CCX rule release pipeline failures — identifies failed stage/job, classifies root cause, and suggests a fix. |
| allowed-tools | Bash(curl:*), Bash(python3:*), Bash(gh pr:*), Bash(gh search:*), Bash(gh api:*), Bash(podman manifest inspect:*), AskUserQuestion |
Triage failures in the CCX rule release pipeline (ccx/ccx-rules-releaser).
gitlab.cee.redhat.com is internal. If the script can't connect, check VPN.GITLAB_TOKEN or GL_TOKEN env var — personal access token with read_api scope.security find-certificate -a -p > ~/.ssl/certs.pem then export SSL_CERT_FILE=~/.ssl/certs.pem. On Linux this is usually not needed.triage_rule_release.py next to this file. Outputs JSON./triage-rule-release # Latest pipeline
/triage-rule-release <pipeline-id> # Specific pipeline
/triage-rule-release <gitlab-url> # Parse from URL
python3 triage_rule_release.py (with optional pipeline ID or URL)The pipeline triggers on a new ccx-rules-ocp tag (or manually with CCX_RULES_TAG variable). Notifications go to #ccx-dev-notifications.
Pipeline stages and jobs are defined in the release.yaml file in the releaser repo. Refer to that file for the current list of jobs and their configuration.
After PRs merge in content-service and data-pipeline, Konflux push builds produce images. The rules-containers-private image is built by the rules-containers pipeline triggered earlier. Verify images exist with podman manifest inspect <image>.
| Image | Tag |
|---|---|
quay.io/redhat-services-prod/obsint-processing-tenant/content-service/content-service | First 7 chars of content-service merge commit SHA |
quay.io/redhat-services-prod/obsint-processing-tenant/data-pipeline/data-pipeline | First 7 chars of data-pipeline merge commit SHA |
quay.io/redhat-services-prod/obsint-processing-tenant/rules-containers/rules-containers-private | CCX_RULES_TAG date (e.g. 2026.06.16) |
Find merge commit SHA: gh pr view <number> --repo RedHatInsights/<repo> --json mergeCommit --jq '.mergeCommit.oid[:7]'
Check Konflux build: gh api repos/RedHatInsights/<repo>/commits/<sha>/check-runs --jq '.check_runs[] | select(.name | test("on-push")) | {name, status, conclusion, completed_at}'
GitHub (content-service, data-pipeline):
gh pr list --repo RedHatInsights/<repo> --state all --search "ccx-rules-ocp" --limit 3
gh pr view <number> --repo RedHatInsights/<repo> --json state,mergeable,statusCheckRollup
GitLab (ccx-rules-metrics, rules-containers, molodec, iqe-ccx-plugin):
curl -s -H "PRIVATE-TOKEN: ${GITLAB_TOKEN:-$GL_TOKEN}" \
"https://gitlab.cee.redhat.com/api/v4/projects/<url-encoded-path>/merge_requests?state=all&per_page=3&order_by=created_at&sort=desc"
URL-encoded paths: ccx%2Fccx-rules-metrics, ccx%2Frules-containers, ccx%2Fmolodec, insights-qe%2Fiqe-ccx-plugin
Jenkins logs (for wait-rules-in-stage-internal, wait-inter-prod, jenkins-exter-pipe-test-prod):
curl -s "https://jenkins-csb-ccx-dev-main.dno.corp.redhat.com/job/<job-name>/<build-num>/consoleText" | grep -B5 "FAILED\|AssertionError\|short test summary"