cluster

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Deploy a group of raw Kubernetes manifests via GitOps/ArgoCD without an underlying application chart, using the manifest-group shell chart. Use when a set of resources (ConfigMap, CRD instance, Ingress, RBAC, Job, etc.) needs to live in its own ArgoCD Application/namespace but doesn't belong to any existing Helm release.

Pull a Helm chart from a repo (or OCI) at a specific version and save it under helm/<group>/ with a versioned directory name. Use when adding or upgrading a vendored Helm chart, when the user asks to vendor a chart, or when following the repo's "add chart to helm/" workflow.

ensure all Helm charts have 'extraResources' support by patching templates/extra-resources.yaml and values.yaml. Run when searching for root charts or when a new chart is added.

Update LiteLLM proxy configuration by translating AI SDK example code (Python/shell) into litellm.yaml model entries. Use when the user provides sample code using NVIDIA NIM, OpenAI, or other AI provider SDKs and wants to add the model to the cluster's LiteLLM proxy.

Enroll a namespace into Istio Ambient Mesh by adding an explicit Namespace resource with the istio.io/dataplane-mode=ambient label via extraResources in the representative ArgoCD Application. Use when the user asks to add a namespace to ambient mesh, enable ambient mode for a namespace, or apply istio.io/dataplane-mode=ambient to a namespace via GitOps.