Add newline separator when concatenating skill body content#46
Merged
rwjdk merged 1 commit intorwjdk:mainfrom Feb 18, 2026
Merged
Conversation
Owner
|
@visasnouski : Thank you for the fix; much appreciated 🙌🙏👍 - Will be out in a nuget in a day or so. |
Owner
|
@visasnouski The fix is now released in lates verion of the nuget |
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
2 participants
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.
This pull request addresses an issue where the body content of agent skills was incorrectly concatenated without proper line separators, leading to malformed or unreadable content in the final parsed skill object. The fix ensures that each line from the file after the front matter delimiter is properly joined with a newline character (\n) to maintain correct formatting and readability of the skill's body text.