Chart Testing CLI
The ct CLI detects changed Helm charts and runs checks so an agent can report findings before infrastructure changes merge.
- 1,647 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Lint reads project files; install deploys charts and runs tests with the selected Kubernetes context’s permissions.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/chart-testingDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Lint reads project files; install deploys charts and runs tests with the selected Kubernetes context’s permissions.
This is third-party code. Review the repository files before installing.
What it does
Chart Testing provides ct for checking Helm charts in Git changes. An agent identifies affected charts, runs lint and schema checks and prepares review evidence. Integration testing can install charts in a selected cluster and run tests. Flags, environment variables and configuration files support local and CI workflows scoped to changed apps. Library charts are linted without standalone installation.
Who it is for. Helm repository maintainers verifying changed charts before release or merge.
Good fit when
- A pull request changes several Helm charts.
- An agent should list affected apps before testing.
- CI needs consistent YAML and chart-metadata checks.
- A test cluster is approved for installation and Helm tests.
Not a fit when
- Integration testing would use an unapproved production cluster.
- The Git base needed for change detection is unavailable.
- You expect a library chart to install as an application.
Example request
List changed charts with ct and run lint only, without installing into a cluster.Limitations
The provided Docker image includes tools; a standalone binary needs Helm, Git and YAML-check dependencies prepared separately. Change detection depends on the selected base branch and available Git history. Install mode creates actual cluster resources under kubeconfig permissions, so use a dedicated test context. Linting needs yamllint and Yamale configurations; verify resolved files for consistent local and CI rules.
How to disable. Remove ct from CI and stop the test run. Inspect and clean chart-installed resources through the test environment’s procedure.
FAQ
How do I list changed charts only?
Use `ct list-changed`.
Can I check without installing?
Yes. Use `ct lint`.
What happens to a library chart?
Installation is skipped while linting remains available.
Which settings take precedence?
CLI flags, then environment variables, then configuration files.
How are environment variables named?
Use the `CT_` prefix and replace option-name hyphens with underscores.
Discussion
No questions or reviews yet.
Related
CLI toolsA Helm alternative for deploying charts to Kubernetes with release plans, resource tracking and encrypted secrets
CLI for full-cycle CI/CD to Kubernetes: image builds, Helm-based deploys and container registry cleanup
31 DevOps skills for Claude Code and Codex: config generators, validators and a Kubernetes debugger for Terraform, Helm, CI and Docker
Kubernetes MCP
MCP Server Kubernetes
MCP server for managing a Kubernetes cluster through kubectl and Helm, with a non-destructive mode
The HULL plugin for Claude Code writes, validates and converts Helm charts whose Kubernetes objects are defined as data in values.
KubeShark skill: the agent finds the failure mode first, then writes manifests, Helm and Kustomize to official practice with a rollback plan
README in short
Releases publish artifact and image signatures. Private chart repositories use separately configured credentials.