Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | update-refs |
| description | 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. |
Updates ref: fields in ccx-data-pipeline SaaS YAML files
(in app-interface) to the latest commit SHA from each repo's
default branch. Skips ref: internal, main, and master.
Does not modify jobs/post-deploy-jobs.yml (app-interface updates those refs automatically).
https://gitlab.cee.redhat.com/service/app-interface.gitRun the script from the skills/update-refs directory:
./scripts/update_refs.sh [--dry-run] [--repo <name-or-url>]... [--local-folder <path>]
| Flag | Description |
|---|---|
--dry-run | Show what would change without modifying files |
--repo <value> | Only update refs for this repo (repeatable). Accepts a full URL or just the repo name. Uses exact match — insights-results-aggregator will not match insights-results-aggregator-cleaner. |
--local-folder <path> | Use an existing local app-interface checkout instead of cloning to /tmp/app-interface. |
# Dry-run for all repos
./scripts/update_refs.sh --dry-run
# Update a single repo
./scripts/update_refs.sh --repo insights-results-aggregator
# Update two specific repos
./scripts/update_refs.sh --repo insights-results-aggregator --repo ccx-notification-writer
# Full URL also works
./scripts/update_refs.sh --repo https://github.com/RedHatInsights/insights-results-aggregator
--dry-run so the user can review changes.--local-folder option.--dry-run and present the output.--dry-run./tmp/app-interface. The user can then cd there
to review and submit a merge request.update-refs-<timestamp> and push the changes.
If not using --local-folder, ask the user for the fork:BRANCH="update-refs-$(date +%Y%m%d)"
git checkout -b $BRANCH
git add data/services/insights/ccx-data-pipeline
git commit -m "chore: update refs"
git push -o merge_request.create \
-o merge_request.remove_source_branch \
-o merge_request.target=master \
-o merge_request.title="chore: update refs" \
fork ${BRANCH} --verbose
/tmp/app-interface. But we always
clone in /tmp in order not to create conflicts with the user's local
app-interface clone.data/services/insights/ccx-data-pipeline, except
jobs/post-deploy-jobs.yml / post-deploy-jobs.yaml.url: + ref: pair, fetches the latest SHA from
the repo's default branch via git ls-remote.main, master, and internal
are intentionally skipped.jobs/post-deploy-jobs.yml is excluded;
app-interface maintains those refs.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.