Mutate ConfigHub Units via function-based edits with preflight checks.
npx skills add https://github.com/confighub/confighub-skills --skill cub-mutate
Please help me install this Agent Skill. Skill: cub-mutate Source: https://github.com/confighub/confighub-skills/tree/main/skills/cub-mutate Command: npx skills add https://github.com/confighub/confighub-skills --skill cub-mutate
Mutating ConfigHub Units safely and deterministically often requires disciplined workflows to avoid hand-edits, ensure proper revision history, and enforce validation through functions.
Update a single field using a function like set-container-image and include a concise change description.
High-intent search queries and answers about installing and using this skill.
To safely mutate Kubernetes YAML configs in ConfigHub, use disciplined, function-based edits via cub instead of hand-edits. This approach enforces preflight checks, preserves YAML provenance, and records proper revision history using a clear change description.
The best way to bulk update ConfigHub Units across multiple Spaces is by using ChangeSets. This method applies filtered changes, enforces preflight checks, and ensures every mutation is traceable through proper revision history and change descriptions.
Yes, ConfigHub supports function-based mutations for Kubernetes resources. You can use dedicated functions like set-container-image, set-replicas, and set-env-var through cub to apply deterministic, validated edits rather than manual YAML modifications.
To ensure proper revision history when updating a single ConfigHub Unit, use cub unit update or cub function set with a clear --change-desc parameter. This records a concise changelog description for every applied mutation.
Yes, you can use cub to apply change descriptions and preflight checks for YAML mutations. The tool enforces validation workflows before applying changes and requires a descriptive changelog entry to maintain accurate revision history.
You should avoid ad-hoc YAML edits when managing ConfigHub Units because they bypass preflight checks and break revision history. Function-based mutations using cub ensure deterministic changes, preserve YAML provenance, and enforce traceable change descriptions.
confighubRoll back a Unit's head to a prior revision using cub unit update --restore.
confighubPromote releases across downstream Units with preflight checks and atomic ChangeSets.
stakpakCentralize Kubernetes configurations across environments using ConfigHub and the cub CLI.
badbsallyyInteract with MCP servers for listing, configuration, authentication, and direct calls.
