k8s-validate

Validate Kubernetes manifests, GitOps structure, and secret-handling checks before merge.

1|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/buenhyden/hy-home.k8s --skill k8s-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-validate
Source: https://github.com/buenhyden/hy-home.k8s/tree/main/.agents/skills/k8s-validate
Command: npx skills add https://github.com/buenhyden/hy-home.k8s --skill k8s-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kubernetes manifests, GitOps structure, and secret-handling checks are error-prone and time-consuming when validating changes prior to review. This Skill provides a structured sequence to validate syntax, lint, verify GitOps structure, and detect secret handling violations in cluster repositories, reducing risk of broken deployments.

Core Features & Use Cases

  • Deterministic validation sequence: runs YAML/schema validation, kube-linter, and GitOps structure checks consistently.
  • Secret-handling enforcement: blocks changes with secret leakage or misconfigurations before merge.
  • Use Case: before merging a PR that updates ArgoCD app manifests, this Skill validates all changes and reports any policy violations.

Quick Start

Run the validation sequence on the changed manifest set to ensure readiness for GitOps review.

Frequently Asked Questions about k8s-validate

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

FAQPage Schema
How do I validate Kubernetes manifests before a GitOps merge?

To validate Kubernetes manifests before a GitOps merge, you need a deterministic workflow that runs YAML schema validation, kube-linter checks, and GitOps structure verification on changed files. This enforces policy compliance and blocks secret violations prior to review.

What is the best way to detect secret leakage in Kubernetes cluster repositories?

Detecting secret leakage in Kubernetes cluster repositories requires automated secret-handling enforcement that scans manifest edits and ArgoCD configurations. This process blocks misconfigurations and prevents sensitive data exposure before changes are merged into the GitOps pipeline.

How do I run kube-linter checks on ArgoCD app manifests?

Running kube-linter checks on ArgoCD app manifests involves applying a structured validation sequence to the changed manifest set. This integrates linting into your CI/CD pipeline to ensure readiness for GitOps review by catching syntax and policy violations.

Can I use this validation sequence for Helm values in a GitOps workflow?

Yes, you can validate Helm values within a GitOps workflow. The validation process applies to changes across manifest edits, ArgoCD configurations, and related GitOps assets, ensuring all Helm value modifications are checked for syntax and structure.

Why does GitOps structure validation fail on my manifest updates?

GitOps structure validation fails on manifest updates when the changes do not adhere to the required repository structure or contain syntax errors. A deterministic validation sequence identifies these specific structural misconfigurations before blocking the GitOps merge.

Do I need additional dependencies to lint Kubernetes manifests for GitOps review?

No additional dependencies are required to lint Kubernetes manifests for GitOps review. The validation operates as a self-contained sequence that performs YAML schema checks, kube-linter analysis, and secret detection directly on the repository assets.