all publishers

openshift

@openshift source repo

185 published skills · page 2 of 2

  1. ▌
    Validate And Fix · openshift
    Run install sync, unit tests, and make verify; auto-fix trivial failures (ruff format/fix, obvious test expectation updates). Use when the user asks to validate, run tests, check the pipeline, or verify changes are clean.
    552 repo stars
  2. ▌
    Investigate CI Failure · openshift
    Investigate CI job failures on a GitHub pull request (checks, Prow, or GitHub Actions). Use when the user pastes a PR URL and asks about CI failures or red checks.
    552 repo stars
  3. ▌
    Echo Token · openshift bundle
    Generate a verification token and write it to disk. Use when asked to produce an e2e test token.
    552 repo stars
  4. ▌
    Find Token · openshift bundle
    Find the hidden verification token. Run the find-token script to retrieve unique DIAG and VERIFY tokens.
    552 repo stars
  5. ▌
    Step Finder · openshift
    Search openshift/release step-registry for existing steps, workflows, and chains before creating new CI components. Use when adding tests, jobs, or step-registry entries, or when asked to find reusable pre/test/post components.
    552 repo stars
  6. ▌
    Add Step Registry · openshift
    Add a new step-registry step (ref YAML + commands.sh) in openshift/release. Use when creating a new CI step, atomic test action, or reusable ref component. Run step-finder first to avoid duplicates.
    552 repo stars
  7. ▌
    Rhdh Ocp Pool · openshift bundle
    List existing RHDH OCP Hive ClusterPool configurations and generate new pool YAML for a target OCP version, with imageSetRef aligned from other pools in the openshift/release repository. Covers OCP pools only, not K8s platforms
    552 repo stars
  8. ▌
    Rhdh Aks Tests · openshift bundle
    List AKS test entries in RHDH ci-operator config files and update the AKS Kubernetes version per branch. Use when listing e2e-aks tests, changing MAPT_KUBERNETES_VERSION for AKS, or checking which AKS K8s version each release branch uses.
    552 repo stars
  9. ▌
    Rhdh Eks Tests · openshift bundle
    List EKS test entries in RHDH ci-operator config files and update the EKS Kubernetes version per branch. Use when listing e2e-eks tests, changing MAPT_KUBERNETES_VERSION for EKS, or checking which EKS K8s version each release branch uses.
    552 repo stars
  10. ▌
    Rhdh Gke Tests · openshift bundle
    List GKE test entries in RHDH ci-operator config files. Use when listing e2e-gke tests or checking which branches have GKE test entries. Unlike AKS/EKS, GKE uses a pre-existing static cluster — version upgrades are performed via the GCP Console.
    552 repo stars
  11. ▌
    Rhdh Ocp Tests · openshift bundle
    List, generate, add, and remove OCP-versioned test entries (e2e-ocp-*) in RHDH ci-operator config files. Covers only OCP cluster-claim tests, not K8s platform tests (AKS, EKS, GKE, OSD)
    552 repo stars
  12. ▌
    Rhdh Ocp Coverage · openshift bundle
    Analyze RHDH OCP version coverage by cross-referencing cluster pools and CI test configs against both RHDH and OCP lifecycle APIs to find gaps, stale configurations, and compatibility mismatches
    552 repo stars
  13. ▌
    Rhdh Aks Lifecycle · openshift bundle
    Check AKS Kubernetes version support status using the official AKS release status API and compare against versions configured in CI config files. Use whenever someone asks about AKS K8s version support, EOL dates, deprecation, or whether the configured AKS version is still GA. Also use when planning AKS K8s version upgrades — run this before using rhdh-aks-tests to make changes.
    552 repo stars
  14. ▌
    Rhdh Eks Lifecycle · openshift bundle
    Check EKS Kubernetes version support status using the official AWS EKS docs source and compare against versions configured in CI config files. Use whenever someone asks about EKS K8s version support, EOL dates, or whether the configured EKS version is still in standard support. Also use when planning EKS K8s version upgrades — run this before using rhdh-eks-tests to make changes.
    552 repo stars
  15. ▌
    Rhdh Gke Lifecycle · openshift bundle
    Check GKE Kubernetes version support status using the endoflife.date API (auto-scraped from Google's GKE release schedule). Use whenever someone asks about GKE K8s version support, EOL dates, or whether the current GKE cluster version is still supported. GKE uses a long-running static cluster whose version is not managed in CI config.
    552 repo stars
  16. ▌
    Rhdh Ocp Lifecycle · openshift bundle
    Check which OCP versions are supported by active RHDH releases and which are end-of-life, using the Red Hat Product Life Cycles API for both RHDH and OCP lifecycle data including EUS phases. Supports OCP 4.x and future 5.x+
    552 repo stars
  17. ▌
    Otel · openshift bundle
    Use this skill to analyze failing CI tests for the OpenShift OpenTelemetry Operator, rerun the specific failing tests (chainsaw-based, junit_otel_* prefix), diagnose whether the failure is a product bug or a test that needs fixing, apply fixes to test source files when needed, and export results to the artifact directory. Trigger whenever $SHARED_DIR/qe-agent-context.json is present with has_test_failures=true for OpenTelemetry Operator tests, or when an engineer asks to debug, rerun, or fix failing OTel QE tests.
    552 repo stars
  18. ▌
    Rhdh Decommission Release · openshift bundle
    Use when decommissioning an end-of-life RHDH release branch by removing CI config, generated Prow jobs, and branch protection from the openshift/release repository
    552 repo stars
  19. ▌
    Tempo · openshift bundle
    Use this skill to analyze failing CI tests for the OpenShift Tempo Operator (TempoStack and TempoMonolithic), rerun the specific failing tests (chainsaw-based, junit_tempo_* prefix), diagnose whether the failure is a product bug or a test that needs fixing, apply fixes to test source files when needed, and export results to the artifact directory. Trigger whenever $SHARED_DIR/qe-agent-context.json is present with has_test_failures=true for Tempo Operator tests, or when an engineer asks to debug, rerun, or fix failing Tempo QE tests.
    552 repo stars
  20. ▌
    Tracing UI · openshift bundle
    Use this skill to analyze failing CI tests for the OpenShift Distributed Tracing UI console plugin (Cypress, junit_distributed-tracing-console-plugin* prefix) - rerun them, diagnose product bug vs test issue vs job configuration, fix test files when needed, and export results. Trigger when $SHARED_DIR/qe-agent-context.json has has_test_failures=true for Tracing UI tests, or when an engineer asks to debug, rerun, or fix failing Tracing UI QE tests.
    552 repo stars
  21. ▌
    Census · openshift bundle
    Use when the user asks for the corpus census, the report population, "how many repos/reports do we actually have", how much duplication is in the numbers, the distinct-vulnerability count, ownership cuts (owned vs upstream vs external-BU), or asks to (re)build the census or corpus manifest. Deterministically resolves the report population via python3 -m traust.cli corpus + $TRAUST_CONFIG_HOME/corpus-config.yaml, quantifies the five duplication vectors, computes distinct vulnerabilities (fingerprint-deduped at HEAD, disposition-adjusted, FP-excluded, hardening separate) per ownership cut, and writes census.{json,md,html} — the denominator authority every other dashboard cites.
    552 repo stars
  22. ▌
    Sla View · openshift
    Use when the user asks about SLA compliance, overdue findings, response/remediation deadlines, breach counts, or escalation lists — e.g. "what's past SLA", "criticals overdue", "are we meeting the 30-day clock", "SLA view for FedRAMP", "who's most overdue". Replays disposition-ledger clocks against a schema-validated SLA policy (default: Red Hat PSIRT VMWM) and emits sla-view.{json,md} with per-team overdue tables and a human-gated escalation digest.
    552 repo stars
  23. ▌
    Repo Graph · openshift bundle
    Build or refresh the portfolio repository graph. Reads every segment of the inputs inventory (`locations.inputs`) by the kind declared in `<inputs>/inventory.yaml` (groups / release-payload / catalog / services; ansible/ excluded by default), cross-references every repo against analysis-results/findings/ coverage (audit/triage/threat-model + severity), and emits repo-graph.{json,dot,gexf,html} + repo-graph-stats.md into analysis-results/graph/. Use when asked to "build the repo graph", "update the portfolio graph", "map repos to findings", "which repos have no coverage", or "what ships kube-rbac-proxy".
    552 repo stars
  24. ▌
    Drift Watch · openshift
    Use when the user asks whether derived artifacts or paired sources are stale or drifting — "is anything stale", "check for drift", "are the feeds/graphs/findings-db current", "did inputs change since the graph was built", "run the drift report" — or on a regular cadence. Runs the deterministic staleness/drift checker over feeds, findings.db, repo-/portfolio-graph vs the inputs inventory, repo-liveness, corpus registration, finding-identity stamping across every audit report, ADR-registry pins, external-tool freshness (installed scanners vs latest upstream releases), docs-product-map version enumeration (declared doc versions vs the live docs.redhat.com landing pages — catches FUTURE product-doc versions the variance lane isn't covering), pqc-facts stamps/schema provenance, and dated policy provenance; writes drift-report.{json,md} to progress-tracker/metrics/drift/.
    552 repo stars
  25. ▌
    Findings DB · openshift
    Use when the user asks an ad-hoc question over the findings corpus that reads like a query — "open criticals by business unit", "which repos have the most confirmed findings", "distinct CWE-1104 exposure across products", "how many findings were validated live" — or asks to build/refresh/query the findings database. Queries the SQLite projection (analysis-results/graph/findings.db) instead of walking 8k JSON files.
    552 repo stars
  26. ▌
    Mine Ledger · openshift bundle
    Use when the user asks to mine the disposition ledger for confirmed true positives, build or refresh the rule-calibration corpus, find rule-pack coverage gaps, check per-rule precision, or produce the opengrep rule-authoring backlog — e.g. "mine the ledger", "what TP clusters have no rule", "how precise are the traust rules", "refresh the rule-mining report". Runs out-of-band from audits; audits themselves feed it via structured scanner_correlation entries.
    552 repo stars
  27. ▌
    Loc Dashboard · openshift bundle
    Use when the user asks how many lines of code have been scanned/audited, wants a LoC breakdown by language or repo across the security-audit campaign, or asks to (re)build the LoC dashboard. Produces gh-languages-cache.jsonl and a self-contained loc-dashboard.html from the campaign manifests.
    552 repo stars
  28. ▌
    Traust Metrics · openshift bundle
    Use when the user asks for campaign metrics, a leadership scoreboard, or to (re)build/refresh progress-tracker/metrics/traust-metrics.md. Deterministically harvests headline numbers from the campaign's derived artifacts (executive summary, validation/fuzz dashboard, threat register, progress-tracker control files) and the harness's own tree/git metadata into one consistently-updatable Markdown scoreboard.
    552 repo stars
  29. ▌
    Triage · openshift bundle
    Triage a batch of raw security findings. Verify each is real, collapse duplicates, re-rank by derived exploitability, and tag with an owner. Takes a directory or file of scanner output and writes <repo>-triage.json + <repo>-triage.md sorted by what actually needs engineering attention. Use when asked to "triage findings", "validate scanner output", "prioritize vulns", or "review the backlog". Runs interactively by default; pass --auto to skip the interview.
    552 repo stars
  30. ▌
    Attack Coverage · openshift bundle
    Use when the user asks for MITRE ATT&CK coverage of the portfolio — "which ATT&CK techniques/tactics do our threats or validated chains cover", "build the ATT&CK Navigator layer", "ATT&CK heat map", or after updating threat models/validations to refresh the coverage roll-up. Deterministically joins validated attack chains, threat-model attack_refs, and finding-category-derived candidates against the pinned vendored ATT&CK table and emits a Navigator layer JSON plus a tactic/technique coverage one-pager.
    552 repo stars
  31. ▌
    Check Alignment · openshift
    Use before committing any new or edited skill to the traust repo, or when asked "are the skills aligned", "did my skill drift from the conventions", "run the alignment check" — runs python3 -m traust.cli check skill-alignment, the cross-skill contract guard the pre-commit hook enforces. Verifies referenced scripts exist, deterministic pre-scan recording conventions (deterministic_steps, judge protocol) travel with the tools that require them, audit-profile skills link the shared report structure instead of restating it, liveness consumers name the census artifact, skill frontmatter matches its directory, and discovery wiring (.claude/.crush symlinks + command wrapper) is complete.
    552 repo stars
  32. ▌
    Check Licensing · openshift
    Use before pushing to the traust repo, after adding or editing any skill, rule pack, doc, or script, or when adopting a new external tool, framework, data feed, or rule pack — runs python3 -m traust.cli check content-licenses to verify no restrictively-licensed framework text has been re-imported (PEACH-adaptation fingerprints, restrictive content-license markers outside the licensing docs, CIS benchmark recommendation-text signatures), and walks the checklist for licensing a NEW external dependency into docs/external-dependencies.md. Use when asked to "check licensing", "run the license check", "did I re-import licensed content", "can we use/ship this tool or ruleset", or "add a license row".
    552 repo stars
  33. ▌
    Findings Trends · openshift bundle
    Use when the user asks whether portfolio security findings are trending up or down, wants a burndown, remediation velocity, MTTR, risk-index, or accepted-risk trend, or asks to (re)build the findings-trends dashboard — e.g. "are we getting better", "findings over time", "how fast are we remediating", "what risk have we accepted". Replays every repo's track-findings disposition ledger against time buckets and emits findings-trends.{json,md,html} with direction arrows per metric.
    552 repo stars
  34. ▌
    Portfolio Graph · openshift bundle
    Use when the user asks code-level portfolio questions or to build/refresh/query the portfolio source-code graph — "which products depend on module X" / CVE blast radius, "top shared libraries", "internal library coupling", "rebuild the portfolio graph", "query the code graph". Distinct from /repo-graph (the organizational coverage graph): this one holds the code-level layers — module dependencies (L1), Kubernetes interfaces (L2), artifacts/SBOM (L3), and symbols (L4), all implemented — in a queryable SQLite database built by python3 -m traust.cli portfolio.
    552 repo stars
  35. ▌
    Threat Register · openshift bundle
    Use when the user asks for a fleet-wide or portfolio-wide view of threats (not findings) — "how many unmitigated critical threats do we have", "threat register", "which products carry the most open threat exposure", "what class-closing mitigations would pay off fleet-wide" — or asks to (re)build the threat register. Deterministically aggregates every *-threat-model.md (and legacy THREAT_MODEL.md) under analysis-results into progress-tracker/metrics/dashboards/threat-register/threat-register.{json,md,html}, keyed by the stable compound key <model-slug>:<Tn>.
    552 repo stars
  36. ▌
    Recall Benchmark · openshift bundle
    Use when the user asks to measure the auditor's detection recall, run the recall benchmark, score a harness release against ground truth, bootstrap/admit benchmark targets, or asks "what fraction of real vulnerabilities do we find". Audits pinned pre-fix refs of repos with known-real findings (self-replay from the disposition ledger, CVE replay, seeded) on clean clones, scores detection with the finding_identity match ladder via match_benchmark.py, and emits benchmark.{json,md} + a metrics-ledger snapshot — recall overall/per-CWE/per-severity/per-language, held-out split, and run-to-run stability.
    552 repo stars
  37. ▌
    Vuln Scan · openshift bundle
    Static source-code vulnerability scan. Reads a target directory (and its threat model — <repo>-threat-model.md, or legacy THREAT_MODEL.md — if present), spawns parallel review subagents per focus area, and writes <repo>-vuln-findings.{json,md} with campaign finding IDs ({REPO_SLUG}-{SHORTSHA}-{NNN}) and the shared severity enum, for /triage to consume. When a <repo>-security-audit.json baseline exists, the scan supplements it: known findings are deduped against the baseline and new verified findings enter the disposition ledger directly (as findings-carrying events; the baseline is never written — gate A15) at not_verified (no triage precondition; triage adjudicates downstream) — /secure-code-audit remains the preferred baseline and /verify-remediation the way to update it after fixes. Read-only — no building, running, or network. Use when asked to "scan for vulns", "review this code for security issues", "find bugs in <dir>", "re-sweep an audited repo", or as the step between /threat-model and /triage.
    552 repo stars
  38. ▌
    Patch · openshift
    Generate candidate fixes for verified security findings. Consumes <repo>-triage.json (preferred; legacy TRIAGE.json accepted), a <repo>-security-audit.json report, *-vuln-findings.json (or legacy VULN-FINDINGS.json), *-pqc-facts.json (actionable first-party PQC blockers only), or an external vuln-pipeline results directory. Pipeline input is delegated to the execution-verified `vuln-pipeline patch` ladder; static-analysis input gets a per-finding patch subagent + independent reviewer and is written as inert diffs and git-am-ready patches for human review. Writes PATCHES/bug_NN/{patch.diff,patch.patch,patch_result.json}, PATCHES.md, and PATCHES.json. Use when asked to "fix the findings", "patch these vulns", "generate fixes", or "close the loop on triage".
    552 repo stars
  39. ▌
    Insecure Patterns · openshift bundle
    Use when the user asks which insecure coding patterns recur across the portfolio, wants findings grouped/ranked by CWE or OWASP ASVS category, asks "what are our top vulnerabilities by pattern", "which repos share CWE-X", or asks to (re)build the insecure-patterns dashboard. Walks every *-security-audit.json under analysis-results/findings/ (owned) and analysis-results/oss-findings/ (upstream, reported as a separate tagged cut), keeps only source-code findings (drops YAML/Dockerfile/Helm config gaps), buckets by primary CWE mapped to ASVS 5.0, and writes insecure-patterns/{top25.md, detailed.md, dashboard.html, .json}.
    552 repo stars
  40. ▌
    Check Harness Docs · openshift
    Use when changing harness skills, scripts, schemas, pipeline stages, or documentation, or when checking for documentation drift before a commit. Verify counts, local paths, inventory coverage, CLI examples, external dependency records, and version consistency against the tree; update stale documentation and rerun the checks.
    552 repo stars
  41. ▌
    Financial Tracking · openshift bundle
    Use when the user asks what the campaign or harness is costing, how spend is trending, which business unit a cost lands on, cost per finding or per repo, whether spend is on budget, or asks to capture/refresh financial tracking over time — e.g. "what did July cost", "spend by business unit", "are we over budget", "cost per critical", "is spend going up", "refresh the financial report". Runs the deterministic spend chain (session actuals → per-lane attribution → business-unit bridge → unit economics → trend) and reports estimates that are always labelled as estimates, with an --invoice seam for reconciling against real billing.
    552 repo stars
  42. ▌
    Refresh Dashboards · openshift bundle
    Use when the user asks to refresh, rebuild, or update all the dashboards — "refresh the dashboards", "rebuild every dashboard", "update the derived views", "run the weekly dashboards job" — or on the weekly orchestration cadence. Runs python3 -m traust.cli dashboard refresh, the packaged "Dashboards rebuild" job from docs/continuous-operations.md: projections first (findings.db, census), then the per-dashboard builders (executive summary, trends, insecure-patterns, validation-fuzz, RBAC/tenancy rollup, SLA view, compliance, ATT&CK coverage, LoC cache-only, dependency-exposure, spend), then the leadership scoreboard last because it harvests the others. Deterministic, ~$0, no agents.
    552 repo stars
  43. ▌
    Rbac Tenancy Rollup · openshift bundle
    Use when the user asks for a portfolio view of RBAC or multi-tenancy findings — "what are our RBAC issues", "top RBAC misconfigurations", "multi-tenancy findings rollup", "which repos have over-permissive RBAC", "tenant-isolation findings summary", "ATT&CK view of our RBAC findings" — or asks to (re)build the RBAC/tenancy dashboard. Deterministically aggregates authorization and tenant-isolation findings from the corpus-resolved report population (disposition-aware, FP-excluded, branch re-audits excluded) into an executive rollup with MITRE ATT&CK candidate-technique heat, a detailed top-misconfigurations report, and a self-contained HTML dashboard under progress-tracker/metrics/dashboards/rbac-tenancy/.
    552 repo stars
  44. ▌
    Countersign · openshift
    Review and sign off pending human decisions in the findings disposition ledger — machine-refuted false positives awaiting an identity-verified countersignature, and queued needs-review items — and record human overrides on any finding, including severity upgrades/downgrades and validity flips in both directions (false positive to true positive via reopen, true positive to false positive via override). Renders each pending decision as a self-contained card (claim + refutation + evidence) so nothing needs to be remembered from the original reports, records decisions through the countersign workbench, and rebuilds the cumulative reports. Use when asked to "countersign findings", "sign off false positives", "review pending refutations", "what's waiting for my signature", "clear the disposition queue", "downgrade/upgrade this finding's severity", "reclassify this finding", or "this finding is actually a false positive / actually real".
    552 repo stars
  45. ▌
    Check Skill Security · openshift
    Use before committing any new or edited skill or script to the traust repo, or when asked "does this skill degrade our security posture", "run the security-posture check", "is this skill safe to add" — runs python3 -m traust.cli check skill-security, the security-posture guard the pre-commit hook enforces alongside the alignment gate. Verifies privileged skills declare allowed-tools confinement, untrusted-content readers carry the adversarial-content doctrine, no git network command takes an ungated non-literal URL (the confirmed-RCE class from the 2026-07 self-audit), no shell-execution constructs or ps-visible Authorization headers, no fixed /tmp state paths, no unpinned runtime installs, no raw-egress tool grants, headless agents under repo-config isolation, and target-build invocations routed through the safe_exec sandbox.
    552 repo stars
  46. ▌
    Pqc Readiness · openshift bundle
    Assess a repository's post-quantum TLS readiness. Use when asked whether a repo can negotiate ML-KEM hybrid TLS, who controls that choice, or to emit a pqc-readiness report. Walks the TLS control chain from platform down to app, consulting capability notes for version meaning.
    552 repo stars
  47. ▌
    Create Fuzzing · openshift bundle
    Use when the user asks to write, scaffold, run, or extend a fuzz harness for a parser/decoder/templater identified in a security-audit report — Go-native by default, plus Python (atheris), JavaScript/TypeScript (Jazzer.js), Rust (cargo-fuzz), and Java (jazzer, manual run) via the language field in targets.json and templates under harnesses/_templates/. Adds a target to targets.json, authors a harness dropped into the audited repo's tree, drives `make clone install build fuzz-<id>`, and triages any crashers into follow-up findings. Offline only: no cluster, cloud creds, or service mocks.
    552 repo stars
  48. ▌
    Fleet Fix · openshift bundle
    Use when the user wants to remediate a SYSTEMIC pattern (one weakness class × N repos — an insecure-patterns CWE entry or a PROGRESS.md rollup like the Konflux mutable-pipelineRef) as one campaign instead of per-finding fixes — "fix this pattern everywhere", "fleet fix", "pin pipelineRefs across the fleet", "batch-remediate CWE-X". Authors one reviewed transform spec with golden tests, applies it across every affected repo via apply_fleet_fix.py (diffs only), and only after human batch approval opens MRs/PRs through the remediate-finding fork flow; merge events flow back through track-findings for pattern burndown.
    552 repo stars
  49. ▌
    Add Inputs · openshift
    Use when the user asks to add one or more GitHub/GitLab repositories or an entire GitHub organization to the repository inventory (`locations.inputs`). Adds entries to the appropriate segment CSV files and generates matching owners.csv rows.
    552 repo stars
  50. ▌
    Crypto Analysis · openshift bundle
    Use when you need to understand a crypto decision point — probe what crypto is configured, trace who owns the decision (governance chain), and confirm with runtime evidence. Probe-driven via python3 -m traust.cli adapters crypto-audit.
    552 repo stars
  51. ▌
    Impact Analysis · openshift bundle
    Use when determining which portfolio repositories are affected by an advisory (CVE, GHSA, MAL-/malicious-package, or another OSV-native id). Queries the portfolio graph for blast radius, then runs language-specific analysis (govulncheck + ELF reachability for Go, the strongest tier; manifest-level analyzers for npm, PyPI, Maven, Cargo, RubyGems, and NuGet; a manifest-level SurfaceAnalyzer for the universal Docker/GitHub Actions/Helm surfaces) to classify every importing repo. Emits a schema-validated artifact consumed by /triage and /verify-remediation.
    552 repo stars
  52. ▌
    Track Findings · openshift bundle
    Use when the user wants to record human triage feedback or machine validation results against the findings of a *-security-audit, *-cloud-config-audit, or *-container-audit report and produce a cumulative status report — ingesting merge-request comments, commits, Jira tickets, interactive human triage, live-validation reports, and remediation-verification reports into an append-only disposition layer, then generating a schema-conformant *-findings-current.{json,md} showing the current validity and resolution of every finding.
    552 repo stars
  53. ▌
    Compliance Check · openshift bundle
    Use when the user asks to assess compliance of a product or deployed cloud environment against PCI DSS, NIST 800-53, FedRAMP High/Moderate, SOC 2 (TSC), or the GDPR technical slice — e.g. "run a compliance check", "assess X against FedRAMP moderate", "SOC 2 posture for this service", "are we meeting 800-53 on this cluster", "compliance across all frameworks". Runs the deterministic assessment runner (code-computed verdicts, evidence bundles, citation gate) and judges only evidence_review controls; emits compliance-assessment.{json,md} + optional OSCAL. "interview" mode is the self-service intake: it walks a service owner through boundary declaration and evidence-review context, writing a validated scope-registry entry and an attestation bundle — attestations are evidence, never verdicts.
    552 repo stars
  54. ▌
    Dependency Watch · openshift bundle
    Use on the daily continuous-operations cadence, or when the user asks to "check for new dependency CVEs", "run the deps lane", "watch dependencies", or "file dependency vulnerabilities" — runs the advisory-driven dependency chain end to end: refresh the vulnerability feeds, sweep new advisories against the audited fleet, run /impact-analysis reachability on hits, and route affected repos' findings into their disposition ledgers as event-carried findings (gate A15 — the baseline is never written), so a newly disclosed dependency CVE becomes an owned, SLA-clocked finding the same day. Orchestrator-neutral — invocable identically from an operator session, cron, Source Code Intelligence, or any enterprise scheduler.
    552 repo stars
  55. ▌
    Isolation Review · openshift bundle
    Use when the user asks to review, assess, or score the tenant isolation of a multi-tenant service — resolving the service's repo set via the portfolio graph, building a customer-facing interface inventory from graph data and existing audit/threat-model findings, rating per-interface complexity, scoring five isolation-hardening dimensions (privilege, encryption, authentication, connectivity, operational hygiene) with cited evidence, and emitting a schema-validated isolation report under analysis-results/isolation/<service-slug>/.
    552 repo stars
  56. ▌
    Secure Rpm Audit · openshift
    Use when the user asks to perform a security audit, security review, or vulnerability assessment of an RPM packaging repository (CentOS Stream / Fedora / RHEL dist-git) — a repo containing a .spec file, downstream patches, and a sources lookaside manifest — using OWASP ASVS, the SEI CERT C/C++ Coding Standards, Fedora Packaging Guidelines, SLSA, and OpenSSF Scorecard.
    552 repo stars
  57. ▌
    Corpus Intake · openshift bundle
    Use when the user wants to register, update, or review a corpus tree or scan engagement — "add a new BU engagement", "register this tree", "onboard <name> scanning work", "why is this tree unregistered", "update the ownership of X" — or when any census/dashboard run reports an unregistered-tree drift warning. Interactively interviews for the registration fields (or takes them as arguments), validates and updates $TRAUST_CONFIG_HOME/corpus-config.yaml through corpus_intake.py (never hand-edited), then re-runs /census so the corpus manifest reflects the change immediately.
    552 repo stars
  58. ▌
    Validation Fuzz Dashboard · openshift bundle
    Use when the user asks for a live-validation dashboard, fuzzing-results dashboard, validation coverage roll-up, or "how many findings were confirmed exploitable / refuted" — e.g. "build the validation dashboard", "combine validation and fuzz results", "what did live validation confirm", "validation false-positive rate". Aggregates every validations/*/*validation*.json report plus FUZZ-CAMPAIGN-SUMMARY.md into one self-contained HTML dashboard.
    552 repo stars
  59. ▌
    Cloud Config Audit · openshift bundle
    Use when the user asks to audit or harden the cloud configuration declared in an IaC checkout (Terraform, CloudFormation, Kubernetes/Helm, ARM/Bicep, Dockerfiles) — e.g. "audit our terraform", "check the IaC for misconfigurations", "run checkov", "harden the cloud config in this repo". Runs the pinned open-source Checkov policy engine fully offline (no cloud API calls, no platform key, declared-layer only by design), then a bounded agent pass that dedupes, suppresses with cited rationale, assigns severity from the rubric, and maps to CWE + control refs, emitting a schema-validated cloud-config-audit report that feeds the standard findings flow.
    552 repo stars
  60. ▌
    Executive Summary Findings · openshift bundle
    Use when the user asks for an executive summary, leadership roll-up, or cross-portfolio dashboard of security-audit findings — e.g. "summarise all findings", "how many criticals do we have", "credential leaks across the campaign", "findings by language", or "rebuild the executive summary". Aggregates every *security-audit.{json,md} report under analysis-results/ into a one-page Markdown brief and a self-contained HTML dashboard.
    552 repo stars
  61. ▌
    Threat Model · openshift bundle
    Build and maintain a threat model for a target codebase. Six modes: "interview" walks an application owner through the four-question framework; "bootstrap" derives a model from code plus past vulnerabilities (CVEs, git history, pentest reports, --context docs) when no owner is available; "bootstrap-then-interview" chains the two; "review" measures an existing threat model's drift against the current code and offers to apply fixes; "update" applies targeted feedback without regenerating; "pr" threat-models a diff and returns an approve/request-changes assessment. Output is always named after the target (<repo>-threat-model.md); legacy THREAT_MODEL.md files are still read and are migrated on write. Emissions share one schema gated by python3 -m traust.cli reporting lint. Use when asked to "threat model", "map the attack surface", "is the threat model still current", "threat model this MR/PR/diff", or "what should we be worried about in this codebase".
    552 repo stars
  62. ▌
    Verify Remediation · openshift bundle
    Use when the user provides a previous secure-code-audit report and a patched version of the scanned repository, and asks to verify that findings have been resolved. Performs a targeted re-audit of each original finding against the patched code using the same frameworks, criteria, and evidence standards as the original secure-code-audit, then emits a structured verification report.
    552 repo stars
  63. ▌
    Validate Findings · openshift bundle
    Use when the user asks to validate, reproduce, exploit, red-team, or live-test security findings against a Kubernetes/OpenShift cluster, operator, WASM module, container, pod, or cluster component. Ingests *-security-audit, *-threat-model, and *-triage reports, builds an attack plan (replay + chained + novel), executes it against an authorized live target under a hard scope guard, and emits a schema-validated *-validation.{json,md} report.
    552 repo stars
  64. ▌
    Operator Priv Profile · openshift bundle
    Use when the user asks whether an operator runs with least privilege, what SCCs/securityContext/namespaces/roles an operator uses or requires, or for a fleet least-privilege inventory of OpenShift core and optional operators. Builds a deterministic per-operator privilege profile from manifests/CSVs (tier 1 — SCC requests, per-container securityContext, namespaces/install modes, complete RBAC enumeration), diffs shipped RBAC against the code's +kubebuilder:rbac markers (tier 2 — surplus grants = least-priv gap), and ships a gated runtime capture for the actually-assigned SCC and effective SA permissions (tier 3, executed only with explicit cluster authorization).
    552 repo stars
  65. ▌
    Security Audit Phased · openshift bundle
    Use when a reviewer wants to steer a security code audit between phases — Phase 1 reconnaissance, Phase 2 prior-vuln pattern analysis, Phase 3 systematic CWE-taxonomy weakness hunt (including PEACH tenant isolation), Phase 4 cross-cutting analysis and final report, Phase 6 reproducer generation, plus review/CVSS/follow-up-seed helpers. Each phase is a separate slash command that reads the previous phase's JSON and writes its own.
    552 repo stars
  66. ▌
    Remediate Finding · openshift bundle
    Use when the user asks to remediate, patch, fix, or produce a code fix for a security finding from the audit campaign — creating a minimal reviewable patch on a private fork, running the repo's own build/test suite, and emitting a schema-validated remediation report.
    552 repo stars
  67. ▌
    Secure Container Audit · openshift
    Use when the user asks to perform a security audit, vulnerability scan, SBOM analysis, or supply-chain assessment of a container image (registry reference, payload image, or batch of images) using skopeo, syft, and grype — covering image configuration, known CVEs in shipped packages, signature/provenance posture, and drift between the image contents and its source repository.
    552 repo stars
  68. ▌
    Generate Team Report · openshift bundle
    Use when the user asks to generate a shareable findings folder, executive summary, or team-specific security audit report for one or more products from the findings directory.
    552 repo stars
  69. ▌
    Inventory Repositories · openshift bundle
    Use when the user asks to list, discover, inventory, or extract the source repositories that ship in a release payload image or an OLM operator bundle/catalog — e.g. "inventory release 4.21", "which repos ship in the foo operator 2.3", "refresh the payload inventory". Writes the per-segment CSV inventory and owners.csv that repo-graph and the dashboards read.
    552 repo stars
  70. ▌
    Validate Browser Finding · openshift bundle
    Use when validating browser-exploitable findings such as CSRF, XSS, or clickjacking against authorized containerized labs with Playwright. Test progressively through authentication, middleware, and ingress defenses.
    552 repo stars
  71. ▌
    Restructure Commits · openshift
    Restructure branch commits into logical component-based commits for HyperShift PRs
    552 repo stars
  72. ▌
    Triage Leaked Infra · openshift
    Assess whether an AWS VPC or infra set from HyperShift CI is safe to delete. Use when the user pastes cleanleaked output and asks 'can I delete this?', 'is this safe to remove?', 'triage this infra', asks about a LEAKED or UNCERTAIN verdict, provides a VPC ID or infraID and wants to know if it's orphaned, or says 'check this VPC'. Also use when the user asks 'should I delete this?' about any AWS resource in the HyperShift CI account.
    552 repo stars
  73. ▌
    Update Konflux Tasks · openshift
    Automatically update outdated Konflux Tekton tasks based on enterprise contract verification logs.
    552 repo stars
  74. ▌
    Konflux Archived Pipelineruns · openshift
    Accesses archived Konflux PipelineRuns, TaskRuns, and pod logs via KubeArchive. Auto-applies when checking Konflux PipelineRun results, investigating enterprise contract failures, or retrieving logs from completed Konflux CI runs.
    552 repo stars
  75. ▌
    Fix Hypershift Repo Robot Pr · openshift
    Fix robot/bot PRs in HyperShift repo by regenerating files and creating a new PR with passing verification
    552 repo stars
  76. ▌
    Test Tag Pipeline · openshift
    Create a manual PipelineRun to test tag pipeline changes before merging.
    552 repo stars
  77. ▌
    Build Ho Image · openshift
    Build and push hypershift-operator container image. Auto-applies when testing HO changes that require deploying to a live cluster.
    552 repo stars
  78. ▌
    Destroy Hc AWS · openshift
    Destroy a HyperShift HostedCluster and all associated AWS infrastructure (VPC, IAM, Route53, etc.).
    552 repo stars
  79. ▌
    Install Ho AWS · openshift
    Install HyperShift Operator with private AWS and external-dns settings.
    552 repo stars
  80. ▌
    Build Cpo Image · openshift
    Build and push control-plane-operator container image. Auto-applies when testing CPO changes that require deploying to a live cluster.
    552 repo stars
  81. ▌
    Feature Development · openshift
    Implement support for a new HCP feature using specialized agents.
    552 repo stars
  82. ▌
    Git Environment · openshift
    Create development environments with git worktrees, branches, commits, and push to remote. Auto-applies for git workflow tasks.
    552 repo stars
  83. ▌
    Konflux Build · openshift
    Create a manual Konflux build from a PR with configurable image expiry (default 30 days)
    552 repo stars
  84. ▌
    E2e Test Runner · openshift
    Provides the ability to run and iterate on HyperShift e2e tests. Auto-applies when implementing features that require e2e validation, fixing e2e test failures, or working on tasks that need live cluster testing.
    552 repo stars
  85. ▌
    Create Hc AWS · openshift
    Create a HyperShift HostedCluster on AWS for development and testing, with optional custom CPO/HO images.
    552 repo stars