fix(skills): remove unquoted ": " from 10 SKILL.md descriptions - #88
Merged
Conversation
10 SKILL.md files had unquoted `: ` sequences inside plain-scalar `description:` values, violating YAML 1.2 §7.3.3. Strict YAML parsers dropped the description and Claude Code fell back to the plugin-prefixed slash name + H1 heading, causing the asymmetric Mac/Windows rendering reported in #87. Fix strategy: - 8 files rephrased (`when:` → `when —`, `flag:` → `flag —`, etc.) - 2 files (mega-pr, pr-ready) converted to folded block scalar (`>-`) to preserve inline slash paths like `/devkit:tri-review` Verified with Ruby Psych strict YAML parser — all 10 files parse cleanly and return non-empty description strings. Closes #87
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
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.
Summary
skills/*/SKILL.mdfiles where unquoted:sequences inside plain-scalardescription:values violated YAML 1.2 §7.3.3, causing strict parsers to drop the description and Claude Code to fall back to the plugin-prefixed slash name + H1 heading.when:→when —,flag:→flag —), 2 files (mega-pr,pr-ready) converted to folded block scalar (>-) because they contain inline slash paths like/devkit:tri-reviewand/commit-commands:commit-push-prthat are natural to keep.descriptionstrings.Rationale for strategy split
when:/flag:.>-) formega-prandpr-readyavoids contorting natural slash-path references. Folded style (>) collapses line breaks back to spaces so the runtime-observable description is unchanged, and strip chomping (-) avoids a trailing newline.Affected files
skills/audit/SKILL.mdflag: outdatedskills/bugfix/SKILL.mdwhen: theskills/deep-research/SKILL.mdwhen: theskills/feature/SKILL.mdfeature: ...,when: theskills/refactor/SKILL.mdwhen: theskills/tri-debug/SKILL.mdwhen: theskills/tri-dispatch/SKILL.mdwhen: theskills/tri-security/SKILL.mdwhen: touchingskills/mega-pr/SKILL.md>-when: theskills/pr-ready/SKILL.md>-when: lintTest plan
ruby -ryaml -e 'YAML.safe_load(frontmatter)'for all 10 files → passes\w+: \Spatterns in any rephrased file (confirmed via grep)/reload-plugins, confirm slash picker shows all 10 skills unprefixed with full descriptions instead of/devkit:<name>+ H1 fallback/reload-plugins, confirm no regression (rendering stays identical)Notes
Closes #87.
Issue #87's per-file token list included a few phantom offenders (
research: c,enforce: s,docs: u,pipeline: v,Skill: d) that don't actually appear in the v2.1.20 files — they were artifacts of the scanning regex. The real count is 11 offending tokens across 10 files, all fixed by this PR.