Verified:GitHub

sre-refresh

Triggers GitLab discovery pipelines to refresh SRE knowledge base documentation from live infrastructure.

Updated Jul 22, 2026

Search Tags:#azure #infrastructure #pipeline #gitlab #sre #refresh #incident

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sre-refresh-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: sre-refresh
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/ai-sre/skills/sre-refresh
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sre-refresh-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Infrastructure documentation drifts out of sync with live Azure environments after cluster, service, or configuration changes, leaving SRE teams with stale reference data during incidents. ## Core Features & Use Cases - Pipeline-Based Refresh: Triggers a discovery pipeline in each product's GitLab KB project that probes live infrastructure and commits drift directly or opens an MR for structural changes. - Product Registry Resolution: Loads the product registry from a shared kb-shared repository, normalizes product slugs, and validates KB project routing before triggering anything. - Dry-Run Preview: The --diff-only flag lists which KB pipelines would be triggered without actually running them. - Use Case: After a new AKS cluster is added to the Emergency Management product, run the refresh to trigger the EM KB pipeline so incident runbooks reflect the new live state. ## Quick Start Run /ai-sre:sre-refresh em to trigger the discovery pipeline for the Emergency Management product's GitLab KB project.

Frequently Asked Questions about sre-refresh

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I refresh SRE infrastructure documentation from live state?▼

Run /ai-sre:sre-refresh with a product slug or no argument for all products. It triggers a discovery pipeline in each product's GitLab KB project that probes live Azure infrastructure and commits routine drift directly to main.

What does the --diff-only flag do in sre-refresh?▼

The --diff-only flag previews which KB pipelines would be triggered for the products in scope without actually running any pipelines. It lists each product, its KB project, pipeline ref, and the variables that would be passed.

Which products are supported by the SRE refresh workflow?▼

All products are KB-managed: em, cpoms-studentsafe, cpoms-staffsafe, training, vm, volunteer, dismissal, eventsafe, smartpass, schoolpass, badge-alert, psw-us, psw-ca, and trigent-safe. The registry is fetched from products.yaml in the kb-shared project.

Does sre-refresh modify SEV thresholds or subscription IDs?▼

No. The refresh never changes SEV thresholds, severity logic, subscription IDs, tenant IDs, or manually curated content like symptom maps and hypothesis patterns. It only updates infrastructure state discovered by the KB pipeline.

Why does the triggered KB pipeline fail immediately?▼

If the KB project does not yet have a .gitlab-ci.yml, the pipeline fails with a no stages or jobs error. This is expected until the CI configuration MRs are merged into the KB repos; the trigger itself remains valid.