yaml-fix-suggestionslisted

# YAML Fix Suggestions -- Auto-trigger Skill Automatically activates when YAML files in Kustomize module directories are modified. ## Activation **Trigger:** Any `.yaml` or `.yml` file is created or edited inside a Kustomize module directory (any directory containing `base/` and `overlays/` structure). **Exclude:** Files under `.claude/`, `.bmad-*/`, tool/agent configuration directories, and any paths excluded by a local `.yamllint.yml`. ## Instructions After the user edits a YAML file, perform these checks silently and only report if issues are found. ### 1. Formatting Check Read the modified file and check against the repo's `.yamllint.yml` configuration (if present). Fall back to these defaults if no `.yamllint.yml` exists: - **Indentation:** 2-space indent, sequences indented (`indent-sequences: true`) - **Trailing whitespace:** Not allowed - **Line length:** 120 characters (or no limit if the repo disables it) - **Document start marker:** Optional - **Duplicate keys:** Not allowed If formatting issues are found, suggest running the repo's formatter. Example: ```bash pre-commit run yamlfmt --files <modified-file> ``` If `pre-commit` is not configured, suggest `yamllint` directly: ```bash yamllint <modified-file> ``` ### 2. Label Compliance Check For any resource with a `metadata:` section, verify standard Kubernetes labels exist. **Recommended Kubernetes labels (check for presence of at least these 4):** | Label | Description | |-------|-------------| | `