gitops-repo-audit

Name: gitops-repo-audit
Availability: InStock
Author: fleet-infra

Audit Flux CD GitOps repositories for Kubernetes schema validity and deprecated API versions.

1|Updated Apr 13, 2026

Search Tags:#security #validation #audit #rbac #gitops #flux #deprecations

Ready to run

npx skills add https://github.com/fleet-infra/gitops --skill gitops-repo-audit-fleet-infra

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitops-repo-audit
Source: https://github.com/fleet-infra/gitops/tree/main/.agents/skills/gitops-repo-audit
Command: npx skills add https://github.com/fleet-infra/gitops --skill gitops-repo-audit-fleet-infra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires flux, awk, git, yq, kustomize, kubeconform, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Audit Flux CD GitOps repositories by scanning local YAML manifests for Kubernetes schema validity and deprecated Flux API versions, enabling teams to identify and remediate issues before deployment.

Core Features & Use Cases

Discovery and validation: scan repos to inventory resources and validate manifests against schemas.
API compliance & security checks: detect deprecated Flux APIs, RBAC/multi-tenancy concerns, and secret handling gaps.
Reporting & remediation: produce a prioritized GitOps report with actionable recommendations for remediation.

Quick Start

Run this skill against a Flux CD GitOps repository to generate a detailed, prioritised report.

Frequently Asked Questions about gitops-repo-audit

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

FAQPage Schema

How do I audit Flux CD GitOps repositories for deprecated APIs and security issues?▼

Audit Flux CD GitOps repositories by scanning local YAML manifests to validate Kubernetes schema correctness, detect deprecated Flux API versions, and identify RBAC and multi-tenancy security gaps. The process produces a prioritized report with actionable remediation recommendations.

How do I validate Kubernetes manifests locally before applying Flux CD GitOps changes?▼

Validate Kubernetes manifests locally by checking YAML files against bundled OpenAPI schemas to ensure resource correctness. This discovery and validation phase inventories resources and confirms manifest validity prior to deployment.

Does this GitOps audit tool work with monorepo and multi-repo Flux CD patterns?▼

The GitOps audit applies its validation and security review workflow to both monorepo and multi-repo Flux CD patterns. It analyzes local YAML manifests consistently across different repository structures to generate a unified prioritized report.

What tools do I need to check Flux CD deprecations and RBAC configurations locally?▼

Checking Flux CD deprecations and RBAC configurations locally requires flux, git, yq, kustomize, kubeconform, and awk. These dependencies drive the discovery, schema validation, and best-practice assessment phases.

What is the best way to generate a prioritized remediation report for Flux CD GitOps security findings?▼

Generate a prioritized remediation report by running a comprehensive security review and best-practice assessment on local GitOps manifests. The resulting output highlights secret handling gaps and RBAC concerns with auditable remediation recommendations.

Why should I scan local YAML manifests for Flux CD schema validity instead of relying on cluster checks?▼

Scanning local YAML manifests for Flux CD schema validity identifies deprecated API versions and configuration issues before deployment. This pre-deployment validation prevents cluster failures and ensures consistent remediation guidance.