fix(skillfrontmatter): handle colons in unquoted description values

[travelliu]

Summary

Fixes #23 — the YAML frontmatter parser now handles colons inside unquoted description values.

Changes

• Remove unused ParseBody and Build functions
• Add FrontmatterBody and HasFrontmatter for cleaner separation of concerns
• Add extractFromRaw fallback when yaml.Unmarshal fails on unquoted colons
• Update cmd_skill_scan.go to use Parse instead of removed ParseBody
• Add tests for colon-containing descriptions and new helper functions

Test plan

• go test ./internal/skillfrontmatter/... passes
• go test ./cmd/multica/... passes
• Standard YAML (no colons) still works
• Quoted descriptions with colons still work
• Unquoted descriptions with colons now work (fallback)

[gemini-code-assist]

Code Review

This pull request refactors the skillfrontmatter package to simplify YAML frontmatter parsing, introducing a fallback parser for unquoted colons and replacing custom parsing logic with strings.Cut. However, the removal of ParseBody introduces a breaking behavioral change by forcing downstream consumers to use the entire file content (including the frontmatter block) as the markdown body. The feedback recommends restoring ParseBody to preserve the original behavior and replacing strings.SplitSeq with strings.Split to maintain backward compatibility with Go versions older than 1.23.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.