[terminal-stylist] Terminal Stylist: Console Output & Charmbracelet (Lipgloss/Huh) Analysis

[github-actions[bot]]

Terminal Stylist Report — Console Output Analysis

Scope: 1167 non-test .go files scanned, prioritizing pkg/. No huh/lipgloss anti-patterns of concern found; the codebase already centralizes styling well.

Key metrics

Pattern	Count
console.* calls (formatters)	2,098
fmt.Print* in production code (non-test, non-testdata)	2 (pkg/cli/status_command.go, pkg/cli/view_command.go)
Files using lipgloss directly	10
Files using huh (interactive forms)	15
Hardcoded ANSI escapes (\x1b[) outside pkg/stringutil/ansi.go	0
Hardcoded hex colors outside pkg/styles	0
Manual strings.Repeat("=", ...) border/separator code	2 (wasm-only fallback files)

Full analysis details

Console formatting package (pkg/console) — mature and consistently used:

• print.go exposes PrintSuccessMessage, PrintInfoMessage, PrintWarningMessage, PrintErrorMessage, PrintCommandMessage, PrintSectionHeader.
• console.go exposes matching Format*/Format*Stderr pairs for every message type (success, info, warning, error, error-chain, section header, list item, table header, command, progress, prompt, verbose), all gated through applyStyle/applyStyleWithTTY, which call tty.IsStdoutTerminal()/tty.IsStderrTerminal() before rendering ANSI. Non-TTY output (pipes, CI logs, redirects) degrades cleanly to plain text — no leaked escape codes.
• RenderTable uses charm.land/lipgloss/v2/table (not manual column alignment), with a TTYFunc override for stderr rendering, alternating row backgrounds via styles.ColorTableAltRow, and colorwriter.Degrade to honor NO_COLOR/COLORTERM/TERM. This is best-practice lipgloss table usage.
• Colors are centralized in pkg/styles/theme.go using lipgloss.AdaptiveColor/LightDark, not hardcoded per-callsite — verified zero hex-color leakage outside the styles package.

fmt.Print usage in production code* — only 2 occurrences, both justifiable:

• pkg/cli/status_command.go:288 — fmt.Print(console.RenderStruct(statuses)): prints a pre-rendered table string; acceptable since the styling work is already done by console.RenderStruct.
• pkg/cli/view_command.go:168 — fmt.Print(output): prints a pre-rendered timeline stream from renderUnifiedTimelineStream. Same pattern.
• All other fmt.Print* hits are in linter testdata/golden fixtures (pkg/linters/.../testdata/), which are intentionally raw and out of scope.
• Minor nit: both call sites use fmt.Print while surrounding code in the same functions uses fmt.Fprintln(os.Stderr, ...) — no functional issue, but for consistency they could route through a console.Print* wrapper that writes to os.Stdout explicitly rather than relying on fmt.Print's implicit stdout target. Not urgent.

Huh (interactive forms) — pkg/console/{confirm,input,list,prompt_form}.go:

• All entry points (ConfirmAction, PromptSecretInput, ShowInteractiveList) correctly check tty.IsStderrTerminal() first and fall back to a plain-text prompt (showTextConfirm, plain error, showTextList) when not a TTY — good accessibility/CI safety.
• Form construction is fully centralized through pkg/console/prompt_form.go's NewForm/NewInputForm/NewSelectForm/NewConfirmForm helpers, each applying .WithTheme(styles.HuhTheme) and .WithAccessible(IsAccessibleMode()) uniformly — no call site constructs a raw huh.NewForm and forgets theming or accessibility, based on the code paths reviewed.
• IsCancelled(err) wraps huh.ErrUserAborted for consistent Ctrl-C/Esc handling across call sites.
• PromptSecretInput correctly uses huh.EchoModePassword and deliberately avoids logging the entered secret value — good security hygiene.
• pkg/styles/huh_theme.go maps the same Dracula-inspired adaptive palette (colorPurpleLight/Dark, colorSuccessLight/Dark, etc.) used for general console output into huh's Focused/Blurred/Group styles, so forms visually match the rest of the CLI.

Opportunities / lower-priority observations:

1. pkg/console/console_wasm.go and pkg/console/layout_wasm.go use manual strings.Repeat("=", width) separators instead of lipgloss layout primitives — acceptable since these are WASM build-tag fallbacks where the full lipgloss/huh stack isn't available, but worth a comment noting why (if not already present).
2. No huh.NewNote, FilePicker, or MultiSelect usage found in the codebase — if future interactive flows need static informational panels or multi-value selection, these huh field types are available and already themed via HuhTheme.
3. Accessibility mode (IsAccessibleMode()) is wired through NewForm and spinner.go/compile_schedule_calendar.go, but is not referenced in confirm.go/input.go/list.go directly — this is fine since they all funnel through NewConfirmForm/NewInputForm/NewSelectForm, confirming no bypass exists.

Recommendations

• No urgent fixes required — console/lipgloss/huh usage is already consistent, TTY-aware, and centralized.
• Optional: route the two remaining fmt.Print calls (status_command.go, view_command.go) through an explicit os.Stdout-targeted console helper for symmetry with the Fprintln(os.Stderr, ...) calls nearby.
• Optional: add a short comment in the wasm-only fallback files explaining why manual separator strings are used instead of lipgloss (build-tag constraint), to prevent future contributors from "fixing" them inconsistently.
• No hardcoded ANSI escapes, no hardcoded hex colors, no unthemed huh forms, and no missing TTY detection were found in production code.

Generated by 💄 Terminal Stylist · auto · 28.7 AIC · ⌖ 5 AIC · ⊞ 8.1K · ◷

• expires on Jul 31, 2026, 1:33 AM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-07-31T09:33:06.573Z.

Closed by Workflow