#508 Make fix-issue skill description YAML-safe#509
Conversation
There was a problem hiding this comment.
Trivial but correct fix: replaces a colon with a dash in the YAML frontmatter description field. A colon : after a value in YAML has special meaning (type indicator), while a dash - does not — so the change makes the description YAML-safe. No functional changes, no test impact, no review concerns.
Reviewed by proxy/@preset/minimax-minimax-m2-7-no-thinking
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe PR updates the ChangesSkill Metadata Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Comment |
Closes #508
Summary
Update the
fix-issueskill frontmatter description so it no longer contains an unquoted:sequence that YAML parsers treat as a mapping delimiter.Test plan
origin/mainfrontmatter fails withmapping values are not allowed in this context..claude/skills/fix-issue/SKILL.mdfrontmatter parses successfully with Ruby YAML.git diff --cached --check.Summary by CodeRabbit
Documentation
Chores