helm-values-precedence-review

Estrelas0

Forks0

Atualizado13 de abril de 2026 às 06:24

Review or change Helm/chart values precedence in this repository. Use when working on global.yaml, chart-name yaml, modules, runtime values, template overrides, or --set merge behavior.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

atframework

atframework/atdtool

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

SKILL.md

readonly

name	helm-values-precedence-review
description	Review or change Helm/chart values precedence in this repository. Use when working on global.yaml, chart-name yaml, modules, runtime values, template overrides, or --set merge behavior.

Helm values precedence review

Start from the implementation, not from old docs. Inspect internal/pkg/util/chart.go first, then the nearest tests.
Confirm the effective merge order for chart defaults, global.yaml, chart-name yaml, modules/*.yaml, runtime/template values, and --set.
Check module enable/disable behavior and whether disabled modules are removed or merely ignored.
For template-related changes, also inspect cmd/atdtool/template.go and related tests.
Keep deep-merge semantics and alias mapping (type_name, func_name, chart name) explicit in both code and tests.
If precedence changes, update tests and docs together:
- internal/pkg/util/chart_test.go
- cmd/atdtool/template_test.go when runtime/template values are affected
- docs/usage/values-and-overrides.md
- docs/usage/modules.md
- docs/usage/merge-values.md or docs/usage/template.md when command behavior changes
Verify with focused tests first, then go test ./....

Mais deste repositório

mesmo repositório

cli-command-change-checklist

atframework/atdtool

Review or implement user-visible CLI command changes in this repository. Use when changing subcommands, flags, help text, defaults, output paths, or command behavior.

2026-04-130

docs-sync-after-code-change

atframework/atdtool

Synchronize documentation after code changes in this repository. Use when implementation changes affect commands, values precedence, template runtime behavior, project structure docs, or examples.

2026-04-130

repo-implementation

atframework/atdtool

Implement or refactor production code in this Go repository. Use when adding features, fixing bugs, changing CLI behavior, or modifying files under cmd/, cli/, internal/, pkg/, or logarchive/.

2026-04-130

repo-testing

atframework/atdtool

Write, repair, or stabilize tests in this Go repository. Use when adding unit tests, reproducing bugs with tests, fixing failing or flaky tests, updating testdata, or improving coverage for changed behavior.

2026-04-130

name	helm-values-precedence-review
description	Review or change Helm/chart values precedence in this repository. Use when working on global.yaml, chart-name yaml, modules, runtime values, template overrides, or --set merge behavior.

Helm values precedence review

Start from the implementation, not from old docs. Inspect internal/pkg/util/chart.go first, then the nearest tests.
Confirm the effective merge order for chart defaults, global.yaml, chart-name yaml, modules/*.yaml, runtime/template values, and --set.
Check module enable/disable behavior and whether disabled modules are removed or merely ignored.
For template-related changes, also inspect cmd/atdtool/template.go and related tests.
Keep deep-merge semantics and alias mapping (type_name, func_name, chart name) explicit in both code and tests.
If precedence changes, update tests and docs together:
- internal/pkg/util/chart_test.go
- cmd/atdtool/template_test.go when runtime/template values are affected
- docs/usage/values-and-overrides.md
- docs/usage/modules.md
- docs/usage/merge-values.md or docs/usage/template.md when command behavior changes
Verify with focused tests first, then go test ./....