github OthmanAdi/planning-with-files v2.38.1
v2.38.1: delimiter swap (--- to ===) to avoid YAML doc-separator collision

12 hours ago

Fixed

Description field garbled in Claude Code skill picker (surfaced via Discussion #153 by @bmyury): the canonical SKILL.md frontmatter declares hooks inline as YAML scalars. Several of those scalars contain '---BEGIN PLAN DATA---' and '---END PLAN DATA---' as plan-injection delimiters (introduced in v2.36.1, reinforced in v2.37 attestation). Frontmatter parsers that split on the literal string --- to locate the closing fence read the first --- inside a hook command as the fence, truncating the YAML mid-string. Claude Code's skill-discovery loader behaves this way, so the description shown in the in-product skill list was a fragment of the hook command tail (BEGIN PLAN DATA---'; head -50 task_plan.md...) instead of the documented description.

Real YAML parsers handled the frontmatter correctly, so hook execution and tamper attestation were never affected; only the displayed metadata was wrong.

v2.38.1 swaps the delimiter shape to ===BEGIN PLAN DATA=== / ===END PLAN DATA=== across:

  • canonical skills/planning-with-files/SKILL.md
  • all five language variants (-ar, -de, -es, -zh, -zht)
  • .codebuddy, .codex, .cursor adapter mirrors
  • clawhub-upload bundle

Same delimiter shape, same model-side framing semantics, no collision with YAML's document separator.

Changed

  • Version bumped to 2.38.1 across 14 SKILL.md variants, plugin.json, marketplace.json, CITATION.cff via scripts/bump-version.py. .continue, .gemini, .pi, .kiro lag intentionally.

Thanks

  • @bmyury for surfacing the description display bug via Discussion #153.

Full Changelog: v2.38.0...v2.38.1

Don't miss a new planning-with-files release

NewReleases is sending notifications on new releases.