infra

Enforce Git-first Infrastructure as Code for Kubernetes cluster modifications.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nirssyan/nirssyan-mono --skill infra-nirssyan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infra
Source: https://github.com/nirssyan/nirssyan-mono/tree/main/.claude/skills/infra
Command: npx skills add https://github.com/nirssyan/nirssyan-mono --skill infra-nirssyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents direct, unmanaged changes to your Kubernetes cluster infrastructure, ensuring all modifications are tracked, auditable, and follow Infrastructure as Code (IaC) principles. It enforces a Git-first workflow for all infrastructure updates, including ConfigMaps and Secrets.

Core Features & Use Cases

  • Infrastructure as Code Enforcement: Mandates that all Kubernetes changes are made through the infra-startup Git repository.
  • ConfigMap & Secret Management: Manages LLM model configurations (ConfigMaps) and API keys (SealedSecrets) via a Git-first workflow.
  • Use Case: When you need to update the replica count for a service, you must first edit the deployment manifest in the infra-startup repository, apply the changes from there, and then commit the modification to Git, rather than using kubectl scale directly.

Quick Start

Use the infra skill to update the image pull secret for the 'my-service' deployment in the 'dev' environment.

Frequently Asked Questions about infra

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

FAQPage Schema
How do I enforce Infrastructure as Code for Kubernetes cluster modifications?

Enforce Infrastructure as Code for Kubernetes by mandating a Git-first workflow through the infra-startup repository, preventing direct kubectl mutations and ensuring all changes are version-controlled and auditable.

What is the best way to update Kubernetes ConfigMaps for LLM models without direct kubectl access?

Update Kubernetes ConfigMaps for LLM models by editing the specific files within the infra-startup Git repository, applying the changes, and committing the modification to Git to prevent direct kubectl mutations.

How do I manage SealedSecrets for API keys in a GitOps workflow?

Manage SealedSecrets for API keys in a GitOps workflow by defining them in the infra-startup repository, ensuring API key changes are version-controlled, auditable, and applied without direct cluster modifications.

Can I scale a Kubernetes deployment directly using kubectl with this workflow?

No, you cannot scale directly with kubectl. You must edit the deployment manifest in the infra-startup repository, apply the changes from there, and commit the modification to Git to maintain Infrastructure as Code.

Why does my Kubernetes GitOps workflow require a specific file structure?

A Kubernetes GitOps workflow requires specific file structures to enforce Infrastructure as Code principles, ensuring all infrastructure operations are version-controlled, auditable, and properly tracked through Git commit practices.