[terminal-stylist] Terminal Stylist: Console Output Consistency Analysis

[github-actions[bot]]

Terminal Stylist Analysis — Console Output Consistency

Scanned 1,179 non-test .go files under pkg/. Console output is already highly centralized: 244 files use pkg/console, 6 use lipgloss directly, 17 use huh, and only 2 production files call raw fmt.Print* outside the console package.

Key Findings

• ✅ Strong centralization: almost all user-facing output flows through pkg/console (console.go, banner.go, spinner.go, list.go, confirm.go, input.go, prompt_form.go), which wraps Lipgloss styling with TTY/NO_COLOR/COLORTERM detection (applyStyleWithTTY, applyStdoutStyleWithTTY, applyStderrStyleWithTTY).
• ✅ Adaptive color scheme: pkg/styles/theme.go defines a custom adaptiveColor type mirroring lipgloss.AdaptiveColor, wired to lipgloss.HasDarkBackground via configureHasDarkBackground, with light/dark pairs for Error, Warning, Success, Info, Purple, Yellow, Comment, Foreground, Background, Border, and TableAltRow — good separation of concerns and testability (background detector is injectable).
• ✅ Huh forms are used consistently for interactive flows (add_interactive_, bootstrap_profile_, run_interactive.go, engine_secrets.go) and themed via pkg/styles/huh_theme.go.
• ⚠️ Minor gaps found (see details).

Files with raw fmt.Print* (non-test, non-linter)

File	Line	Note
pkg/cli/status_command.go	288	fmt.Print(console.RenderStruct(statuses)) — acceptable: output is already styled by console.RenderStruct; fmt.Print is just the sink.
pkg/cli/view_command.go	168	fmt.Print(output) — same pattern, output appears pre-rendered. Low risk but consider routing through a console.Print/console.Write wrapper for consistency and future TTY-aware behavior.

Two additional fmt.Print* hits are in pkg/linters/hardcodedfilepath/hardcodedfilepath.go (a linter analyzer, not user console output) and its testdata — not in scope for this report.

Lipgloss usage details

• pkg/console/console.go: table rendering (buildTableStyleFunc), borders (DoubleBorder, NormalBorder), alignment (lipgloss.Center, lipgloss.Left), vertical joins (lipgloss.JoinVertical) — all gated behind TTY checks before styling is applied, which correctly avoids leaking ANSI codes into pipes/redirects.
• pkg/console/banner.go: banner box styling.
• pkg/cli/compile_schedule_calendar.go: calendar rendering, isolated usage — good.
• pkg/logger/logger.go: namespace coloring for debug logs — appropriate use of Lipgloss for structured debug output.
• pkg/styles/theme.go / huh_theme.go: central style/theme registry consumed by the rest of the codebase — this is the right architecture (single source of truth for styling).

No hardcoded ANSI escape sequences or manual color codes were found outside Lipgloss — a good sign of discipline.

Huh usage details

Forms are spread across well-scoped files by responsibility: add_interactive_orchestrator.go, add_interactive_git.go, add_interactive_auth.go, add_interactive_workflow.go, add_interactive_schedule.go, add_interactive_engine.go, bootstrap_profile_github_app.go, bootstrap_profile_helpers.go, engine_secrets.go, run_interactive.go, and generic wrappers in pkg/console (spinner.go, list.go, confirm.go, input.go, prompt_form.go). This modular split (one concern per file) matches the repo's code-organization conventions and keeps forms testable.

No obvious accessibility regressions were found in the sampled entry points; pkg/console wrappers appear to be the common interactive surface, so accessibility mode (if configured) benefits all callers uniformly.

Recommendations

1. Low priority: route status_command.go:288 and view_command.go:168 through a console sink function (e.g., a thin console.Print/console.Write) instead of calling fmt.Print directly, purely for consistency/greppability — functionally they're already safe since content is pre-styled.
2. No urgent changes needed — the codebase already follows Lipgloss/Huh best practices: adaptive colors, TTY-gated styling, centralized theme, and a single console abstraction layer used by ~21% of all non-test Go files.
3. Consider a lightweight lint/grep CI check (or go vet-style analyzer, consistent with existing pkg/linters/*) to flag any new raw fmt.Print* calls in pkg/cli outside the console package, to preserve this consistency going forward.

Generated by 💄 Terminal Stylist · auto · 20.6 AIC · ⌖ 3.4 AIC · ⊞ 8.2K · ◷

• expires on Aug 4, 2026, 2:00 AM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-08-04T10:00:40.758Z.

Closed by Workflow