fix(skill): tolerate unparseable SKILL.md frontmatter in kit init

[gorkem]

What

Make kit init recover the name and description from a skill directory's SKILL.md even when the frontmatter isn't strictly valid YAML.

Why

For a directory with a root SKILL.md, kit init derives the Kitfile package name/description from the frontmatter. ParseSkillFrontmatter ran a single strict yaml.Unmarshal over the whole block and discarded any error, returning nil. A description containing an unquoted colon — e.g. ... on a pull request: "address the comments" — is not valid YAML (mapping values are not allowed in this context), so all metadata was silently dropped and the generated Kitfile had no name or description. Such descriptions are extremely common in real skills.

How

• Strict-first, lenient-fallback in ParseSkillFrontmatter: try strict YAML first (preserving full YAML semantics, including the multi-line block-scalar descriptions the SKILL.md format permits); only if that fails, fall back to a lenient line-based parse of the known keys (name, description, license) that tolerates colons/quotes/# in prose values.
• No more silent failure: kit init now logs a warning when a SKILL.md is found but no name/description could be recovered.

The lenient path only ever runs on input that already failed strict YAML, so well-formed frontmatter is never mis-parsed.

Validation

• go test ./pkg/lib/skill/... ./pkg/lib/kitfile/generate/... ./pkg/cmd/kitinit/... — pass
• Added table-test cases: unquoted colon in description, quoted-scalar unquoting, block-scalar (strict) description, and updated the existing malformed-YAML case to assert lenient recovery
• gofmt, go vet, go build, addlicense --check, go mod tidy — clean
• Manually verified against a real skill directory: kit init now emits both package.name/package.description and the prompt's name/description

[Copilot]

Pull request overview

This PR improves kit init’s ability to derive package and prompt metadata from a skill directory’s SKILL.md by parsing frontmatter robustly: attempting normal YAML parsing first, then falling back to a lenient line-based extraction when the YAML is malformed (e.g., unquoted colons in prose descriptions). It also adds a warning when metadata can’t be recovered and expands test coverage around these cases.

Changes:

• Implement strict-first YAML parsing with a lenient fallback for name, description, and license in ParseSkillFrontmatter.
• Add warning logging when SKILL.md exists but no name/description can be extracted for Kitfile generation.
• Extend unit tests to cover real-world malformed frontmatter cases (unquoted colon, quoted scalars, block scalars).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
pkg/lib/skill/skillfile.go	Adds strict YAML parse with lenient fallback parser and scalar unquoting helper.
pkg/lib/skill/skillfile_test.go	Adds/updates table tests to assert description parsing across strict and lenient paths.
pkg/lib/kitfile/generate/skill.go	Logs a warning when no name/description can be recovered from SKILL.md.
pkg/lib/kitfile/generate/skill_test.go	Updates malformed-YAML test to expect lenient recovery; adds colon-in-description case.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.