fix(skills): repair SKILL.md YAML frontmatter parse error#1487
Conversation
… error
The description scalar contained an unquoted colon-space ("including the
CLI: how to model users"), which YAML interprets as a nested mapping,
breaking frontmatter parsing with "mapping values are not allowed in
this context." Wrap the value in single quotes (the string contains
embedded double quotes but no apostrophes).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe ChangesSKILL Metadata Formatting
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Greptile SummaryThis PR fixes a YAML frontmatter parse error in
Confidence Score: 5/5Safe to merge — one-line YAML quoting fix with no logic or content changes. The change wraps an unquoted YAML scalar in single quotes to fix a well-understood parse error. The description content is byte-for-byte identical; only the quoting delimiters are added. There are no logic changes, no new dependencies, and no other files touched. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["SKILL.md frontmatter loaded"] --> B{description quoted?}
B -- "No (before fix)" --> C["YAML parser sees ': ' mid-scalar"]
C --> D["❌ Parse error: mapping values not allowed in this context"]
B -- "Yes (after fix)" --> E["Single-quoted scalar parsed correctly"]
E --> F["✅ All 9 frontmatter keys load successfully"]
Reviews (1): Last reviewed commit: "fix(skills): quote SKILL.md description ..." | Re-trigger Greptile |
There was a problem hiding this comment.
Pull request overview
Fixes a YAML frontmatter parse error in the Stack Auth skill definition by quoting a description value that contains a : sequence, which YAML otherwise interprets as a mapping delimiter.
Changes:
- Wrapped the
descriptionscalar in single quotes inskills/stack-auth/SKILL.mdto make the frontmatter valid YAML.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
What
The
descriptionfield inskills/stack-auth/SKILL.mdfailed to parse as YAML, surfacing on GitHub as:Why
The
descriptionwas an unquoted YAML scalar containing a colon-space sequence:In YAML,
:inside an unquoted scalar is parsed as a key/value mapping, which is illegal mid-value — hence "mapping values are not allowed in this context."Fix
Wrapped the
descriptionvalue in single quotes. Single quotes (not double) because the string already contains embedded double quotes ("stack auth","skill") but no apostrophes, so no escaping is needed.Verified the frontmatter now parses cleanly — all 9 keys (
name,description,version,author,tags,testingTypes,frameworks,languages,domains) load viayaml.safe_load.Notes
@stackframe/dashboardtypecheck failure on this branch comes from a stale generated.next/dev/types/routes.d.tsbuild artifact and is not touched by this PR.Summary by cubic
Fixes YAML frontmatter parsing in skills/stack-auth/SKILL.md by quoting the description, removing the “mapping values are not allowed in this context” error. Wrapped the description in single quotes to prevent the
CLI: how...colon-space from being parsed as a mapping.Written for commit b8866bd. Summary will update on new commits. Review in cubic
Summary by CodeRabbit