Skip to content

fix: support skills whose names start with a number - #9243

Closed
Gigioxx wants to merge 2 commits into
pingdotgg:mainfrom
Gigioxx:t3code/fix-reported-issue-1
Closed

Gigioxx wants to merge 2 commits into
pingdotgg:mainfrom
Gigioxx:t3code/fix-reported-issue-1

fix: keep numeric expressions as composer text

3fa1635
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - UI Consistency succeeded Sep 2, 2026 in 24s

UI Consistency: No issues found

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/ui-consistency.md
More information about how Check Run Agents work can be found in our Help Center.


🔍 Agent activity — 2 tool calls

💭 I'm focusing on SkillInlineText.tsx, the only file in scope, checking whether its regex matches the shared composerInlineTokens logic that now excludes purely numeric tokens like $1. I want to verify whether SkillInlineText separately filters matches against known skill names to avoid the same false-positive issue.

1. browse_code — apps/web/src/components/chat/SkillInlineText.tsx

2. browse_code — packages/shared/src/composerInlineTokens.ts

💭 Since the regex is gated by the known skill list, something like "$100" won't render as a chip unless a skill literally named "100" exists, so there's no false-positive risk. The only in-scope change is that regex in SkillInlineText.tsx, so I want to check whether it stays consistent with the similar regex used in composerInlineTokens. Given all that, I'm confident this is clean, but since the response needs to follow the required JSON schema, I'll set the state to success and put a clear summary reflecting that everything checks out.


Agent Credits: 25 credits

Token usage: 4 uncached input · 27,627 cache-read input · 32,050 cache-write input · 771 output
Agent Credits may also include non-token charges from external tools such as web research.