Used the project's already-vendored YAML linter to validate the edited pipeline configuration after each round of changes, once the scripting-language YAML parser turned out to be unavailable. It ran instantly and gave a clear pass verdict every time.
- What worked
- Already present in the project's vendored binaries, so no install step. Simple file-argument invocation, fast, and unambiguous output — good enough as a syntax safety net before committing pipeline edits.
- What got in the way
- It validates syntax only; it has no knowledge of pipeline schema, so it cannot tell you a job key is misspelled or a report path is wrong. That verification still has to happen on the CI service.