processing-tools

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 CCX rule release pipeline failures — identifies failed stage/job, classifies root cause, and suggests a fix.

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.

Triage and fix failing Konflux/MintMaker dependency bump PRs (bot-authored, auto-merge enabled). Use when a Renovate/MintMaker PR is stuck due to CI failures. Covers Go and Python repos in the RedHatInsights org.

Update SaaS file refs in app-interface to the latest commit SHAs. Use when the user says "update refs", "bump refs", "promote", or asks to update ccx-data-pipeline service references.

Build a review-oriented Markdown (or JSON) report for a list of GitHub PRs: links, title, description excerpt, CI rollup status, line and file stats, and optional unified diffs. Use when the user pastes multiple PR URLs, asks for a PR batch table, "review these PRs", or wants CI/diff summaries across several pulls.

Resolve a CVE vulnerability issue from Jira. Reads the CVE details, assesses impact, and either marks "not affected" with a Jira comment and transition, bumps the affected dependency, or implements a code fix. Use when the user says "cve", "resolve CVE", or provides a CVE Jira issue.