Fix YAML frontmatter parse error in security-review's description - #57
Merged
Atharva0506 merged 1 commit intoOct 1, 2026
Merged
Conversation
The description field's unquoted value contained "general classes: ..." — a bare colon+space mid-sentence, which GitHub's YAML frontmatter preview (and any strict YAML parser) reads as the start of a new mapping key, producing "mapping values are not allowed in this context." Rephrase to avoid the colon; no functional change to the skill. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 10 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configurationConfiguration used: Repository: AOSSIE-Org/ThruBox-Server/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
documentation
Contributor
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.
Addressed Issues:
No related issue — GitHub's file-preview page shows a YAML parse error on
skills/security-review/SKILL.md's frontmatter ("mapping values are not allowed in this context at line 2 column 776").Screenshots/Recordings:
Not applicable — one-line text rephrase, no application behavior changes.
Additional Notes:
The
descriptionfield is one long unquoted YAML scalar, and it contained the phrase "...Also covers general classes: injection, auth flaws, ..." — a bare colon+space mid-sentence. YAML reads:anywhere in a plain scalar as the start of a new mapping key, so GitHub's frontmatter preview (and any strict YAML parser) fails on it. Rephrased to "general classes such as injection, ..." to drop the colon. This has been in the skill's description since the very first version; only now surfaced as a visible error.Also pushed the same one-line fix to the sibling PRs on ThruBox-Client, Chainvoice, and IndexedDB-Import-Export, so all four stay identical.
Checklist
This PR was written with Claude Code (model: Claude Sonnet 5), including the skill definitions themselves and this description.
🤖 Generated with Claude Code