From fcea3560b32cc5b1434c8897a56e96075f1e62fe Mon Sep 17 00:00:00 2001
From: Alexey Kulakov <uni_que@me.com>
Date: Wed, 21 Oct 2026 01:17:01 -0700
Subject: [PATCH] docs(track-work): put HTML tags in PR titles in backticks

release-plan copies PR titles into the release notes, and a bare <select> in
one turned the rest of the 4.0.0 notes into one unformatted block.

Signed-off-by: Alexey Kulakov <uni_que@me.com>
---
 .claude/skills/track-work/SKILL.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.claude/skills/track-work/SKILL.md b/.claude/skills/track-work/SKILL.md
index 5e35233c6f..ee3d1a5ce9 100644
--- a/.claude/skills/track-work/SKILL.md
+++ b/.claude/skills/track-work/SKILL.md
@@ -13,6 +13,7 @@ Planning lives in two GitHub Projects owned by the IBM org and linked to this re
 ## Pull Requests
 
 - **One release label:** `breaking`, `enhancement`, `bug`, `documentation` or `internal`. release-plan won't plan a release while a merged PR has none.
+- **HTML tags in the title go in backticks** (`` `<select>` ``): release-plan copies titles into the notes as they are, and a bare `<select>` swallows everything after it.
 - **`preview`** for visual changes; it deploys a Storybook preview.
 - **Milestone `Stable`** for work before the stable release.
 - **`Closes #N`** for the issue it finishes. A parity-check issue also needs `--mark-synced` (see [implement-component](../implement-component/SKILL.md)).