Repository navigation
UI Consistency: 1 issue found
apps/web/src/components/usage/UsagePage.tsx(lines 620-621, 645): call sites overrideSkeleton's base color withbg-muted-foreground/10; the repeated fainter tone should be a variant/prop on theSkeletonprimitive.
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.
Reviewed changed lines in apps/web/src/components/pullRequest/PullRequestGhosts.tsx, apps/web/src/components/ui/skeleton.tsx, apps/web/src/components/usage/UsagePage.tsx, and apps/web/src/index.css. The keyframe/animation changes in index.css are animation definitions, which are explicitly acceptable as global CSS.
🔍 Agent activity — 4 tool calls
💭 I'm checking the diff for UI consistency issues, and I notice UsagePage's Skeleton call overrides the primitive's base color with a custom class string instead of using a proper variant — flagging that as a violation worth fixing at the component level. Since three call sites repeat the same
bg-muted-foreground/10override, that pattern should become a dedicated Skeleton variant rather than a one-off class. There's also a radius override at another call site that's more borderline, and I want to check whether PullRequestGhosts is applying the skeleton animation directly to raw divs instead of using the Skeleton primitive, so I'll pull up the actual files to confirm.
1. browse_code — apps/web/src/components/pullRequest/PullRequestGhosts.tsx
2. browse_code — apps/web/src/components/ui/skeleton.tsx
💭 I'm noticing GhostBar re-implements Skeleton's primitive rather than composing it, but that line itself isn't part of the diff—only the header comment and container class changed. Since the rule is to flag only violations introduced by changed lines, I'm leaning toward skipping this even though the updated docstring hints at the shared styling duplication. The more solid finding is UsagePage overriding Skeleton's base color at multiple call sites, which should really be a variant rather than a repeated class override—that feels distinct from a prior resolved opacity issue. There's also a radius override elsewhere in the diff, but since Skeleton is commonly reshaped with radius/size classes across the codebase, flagging that would just be noise, so I'm focusing on the repeated color override instead and want to verify how other Skeleton usages in the repo typically handle tone.
3. browse_code — List all call sites of the Skeleton component from apps/web/src/components/ui/skeleton.tsx that pass a className overriding the background color (e.g. bg-muted, bg-muted-foreground/10, opacity-*). Give file:line and the className.
💭 Looking at UsagePage around line 620, I notice the same faint-tone class string repeated across three call sites instead of being extracted into a Skeleton variant — this fits the pattern worth flagging as a repeated one-off treatment. I'll post an inline comment on that pair of lines noting it should become a shared variant.
4. modify_pr — Submitted review with 1 inline comment
Agent Credits: 46 credits
Token usage: 18 uncached input · 116,455 cache-read input · 43,763 cache-write input · 3,890 output
Agent Credits may also include non-token charges from external tools such as web research.