From kubestellar-deploy
Detect drift between git manifests and what's deployed in clusters
How this skill is triggered — by the user, by Claude, or both
Slash command
/kubestellar-deploy:gitops-driftThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Compare a git repository against cluster state to find configuration drift.
Compare a git repository against cluster state to find configuration drift.
detect_drift to compare git manifests against cluster staterepo: Git repository URL (required)path: Path within repo (optional)branch: Branch name (default: main)clusters: Target clusters (all if not specified)Do not use any other tools besides the kubestellar-deploy MCP tools.
npx claudepluginhub kubestellar/claude-plugins --plugin kubestellar-deployDetects, audits, and remediates drift between declared infrastructure-as-code and actual deployed state. Use for Terraform plan diffs, Kubernetes kubectl diff, or AWS Config drift detection.
Detects infrastructure drift between actual cloud state and IaC definitions using terraform plan, cloudformation drift detection, or pulumi. Triggered by phrases like 'check for drift'.
Implements GitOps continuous delivery with Argo CD or Flux: app-of-apps patterns, automated sync policies, drift detection, multi-environment promotion. For declarative Kubernetes management from Git.