You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: skills starting with a number are discovered, but the badge is not rendered inline properly #9235
I reproduced this on current main. The skill-token patterns currently require an ASCII letter as the first character across shared composer parsing, web/mobile timeline rendering, and Claude dispatch. I’d like to submit a focused fix that accepts digit-leading discovered skill names and adds regression coverage across those surfaces.
Fixed in #9244. The PR updates numeric-leading skill references across shared composer parsing, web/mobile rendering, and Claude dispatch, with regression coverage for each affected surface.
Before submitting
Area
apps/desktop
Steps to reproduce
User invokes their skills by typing
$<skillname>e.g.,:
$SkillExpected behavior
Skills starting with a n should properly render the badge inline.
e.g.,
$fromSpec →

$2spec →

Actual behavior
Skills starting with a n do not properly render the badge inline.
e.g.,
$fromSpec →

$2spec →
$2spec
Cap.2026-09-01.at.16.59.55.mp4
Impact
Cosmetic issue
Version or commit
No response
Environment
macOS Golden Gate 27.0 (26A5416b)
Logs or stack traces
Screenshots, recordings, or supporting files
Cap.2026-09-01.at.16.59.55.mp4
Workaround
No response