fix: add strict YAML validation for plugin frontmatter#399
Merged
Conversation
Adds a test suite that validates every agent and skill markdown file in both plugins parses with strict YAML. Catches unquoted colons in description fields before they reach users via install. Also adds a checklist item to AGENTS.md reminding contributors to quote descriptions containing colons. Closes #351
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prevents unquoted colons in frontmatter descriptions from breaking
install --to opencode/codex(fixes #351, fixes #349). Three lightweight layers:parseFrontmatternow catches YAML errors and re-throws with the file path and a hint: "quote frontmatter values containing colons". Previously the raw js-yaml exception gave no file context.🤖 Generated with Claude Opus 4.6 (1M context, extended thinking) via Claude Code