Repository navigation
fix(data-ai): use valid YAML for meta-build options - #256
Merged
Merged
Conversation
Co-authored-by: Michael Vitrano <vitrano@adobe.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Parses each SKILL.md with a strict YAML parser and requires a name matching its directory and a non-empty description. Adds the missing descriptions to the x-* skills and applies the meta-build YAML fix to the tracked .agents copy. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
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.
The
optionsfrontmatter in themeta-buildskill usedkey = value, which isn't valid YAML. It now useskey: value.Patch by Michael Vitrano. Bumps the lockstep version to 0.10.31.
🤖 Generated with Claude Code