skills.rest
alex-voloshin-dev
alex-voloshin-devCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gitops-detection

Detect GitOps controllers in Terraform and Helm repositories to route changes through pull requests.

2|Updated Mar 19, 2026
Search Tags:#automation#compliance#infrastructure#helm#terraform#gitops
One-click install
npx skills add https://github.com/alex-voloshin-dev/ai-skills --skill gitops-detection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitops-detection
Source: https://github.com/alex-voloshin-dev/ai-skills/tree/main/plugin/skills/gitops-detection
Command: npx skills add https://github.com/alex-voloshin-dev/ai-skills --skill gitops-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents accidental manual infrastructure changes in environments managed by GitOps controllers, ensuring that changes are routed through the correct version-controlled PR process instead of local imperative commands.

Core Features & Use Cases

  • Controller Detection: Automatically identifies the presence of Argo CD, Flux, Atlantis, HCP Terraform, Spacelift, or env0.
  • Routing Logic: Provides clear instructions on whether to proceed with local commands or switch to a Git-based pull request workflow.
  • Use Case: Before running a terraform apply, the agent uses this skill to verify if the infrastructure is managed by Atlantis or HCP Terraform, preventing unauthorized local state modifications.

Quick Start

Run the gitops-detection skill to verify if the current infrastructure repository requires a pull request instead of a local apply command.

Frequently Asked Questions about gitops-detection

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

FAQPage Schema
How do I prevent manual Terraform apply overrides in GitOps workflows?▼

To prevent manual Terraform apply overrides in GitOps workflows, you can detect GitOps controllers like Atlantis or HCP Terraform to enforce version-controlled PR processes instead of local imperative commands.

How does GitOps controller detection work for infrastructure repositories?▼

GitOps controller detection works by pattern matching against repository markers and configuration blocks to identify automated reconciliation layers like Argo CD, Flux, or Spacelift within your infrastructure repositories.

Does this GitOps detection method support Helm and Terraform configurations?▼

Yes, this GitOps detection method supports both Helm and Terraform workflows where imperative local execution conflicts with automated reconciliation loops managed by controllers like env0 or Atlantis.

What is the best way to check if my infrastructure requires a pull request instead of local commands?▼

The best way to check if your infrastructure requires a pull request is to scan for GitOps controller presence and routing logic, which instructs you whether to proceed with local commands or switch to a Git-based PR workflow.

Why should I not run local commands when my infrastructure is managed by Flux or Argo CD?▼

You should not run local commands when managed by Flux or Argo CD because local imperative execution conflicts with automated reconciliation loops, causing unauthorized state modifications that bypass correct change management procedures.

Related Skills

Explore More Software Engineering Skills→
CatsofsufferingCatsofsuffering
5

infrastructure

Guide engineers in designing Kubernetes, Helm, Kustomize, and GitOps infrastructure.

Community
Advanced
48Nauts-Operator48Nauts-Operator
3

gitops-workflow

Implement GitOps workflows with ArgoCD and Flux for automated Kubernetes deployments.

Community
Advanced
way-platformway-platform
3

spacelift-terraform

Manage Spacelift stacks, contexts, policies, and worker pools via Terraform GitOps workflows.

Official
Advanced
msaad00msaad00
29

agent-bom-enforce

Intercept and enforce user-defined policies on MCP tool calls via a runtime proxy.

Community
Advanced