[terminal-stylist] Terminal Stylist: Console Output Analysis

[github-actions[bot]]

Overview

This analysis covers 937 Go source files in pkg/ (non-test) for console output patterns, Lipgloss styling practices, and Huh form implementations.

Metric	Count
Source files analyzed	937
Files importing pkg/console	200
Files importing pkg/styles	24
Files using Lipgloss directly	6
Files using Huh (charm.land/huh)	13
Raw fmt.Print* calls (pkg/)	~3,000
Raw fmt.Print* to stdout in pkg/cli/	~102

---

Lipgloss Usage

✅ Strengths

• Centralized palette — all color/style definitions live in pkg/styles/theme.go. No hardcoded hex colors found outside that file.
• Full adaptive color system — every color uses compat.AdaptiveColor{Light: ..., Dark: ...} from charm.land/lipgloss/v2/compat, automatically switching between Dracula-inspired dark and accessible light variants.
• TTY-gated styling — console.applyStyle() wraps every lipgloss.Style.Render() call; styles are stripped for pipes and redirects.
• Namespace-colored logger — pkg/logger/logger.go uses a palette of 12 adaptive Lipgloss styles, hash-assigned per namespace.
• Schedule heatmap — compile_schedule_calendar.go uses dedicated styles.ScheduleCalendar{Empty,Low,Medium,High,Critical} styles for intensity bands.
• ANSI cursor control — terminal.go uses raw ANSI sequences only for cursor movement/clear (\033[H\033[2J, \033[K) where Lipgloss has no API — appropriate and TTY-gated.
• Border consistency — styles.RoundedBorder, NormalBorder, ThickBorder are declared centrally; ErrorBox and InfoSection renderers use them uniformly.

Lipgloss color palette (adaptive)

Name	Light	Dark (Dracula)	Use
Error	#D73737	#FF5555	Errors, highlights
Warning	#E67E22	#FFB86C	Warnings, selectors
Success	#27AE60	#50FA7B	Success, list headers
Info	#2980B9	#8BE9FD	Info, hints
Purple	#8E44AD	#BD93F9	File paths, commands, banner
Yellow	#B7950B	#F1FA8C	Progress, attention
Comment	#6C7A89	#6272A4	Muted text, line numbers
Foreground	#2C3E50	#F8F8F2	Primary text
Background	#ECF0F1	#282A36	Highlighted backgrounds
Border	#BDC3C7	#44475A	Borders, tree branches

---

Huh Form Usage

✅ Strengths

• Custom theme — pkg/styles/huh_theme.go provides styles.HuhTheme, a huh.ThemeFunc that maps the Dracula palette to all Huh field states (focused, blurred, selected, error, navigation). Applied consistently with .WithTheme(styles.HuhTheme) across all 13 files.
• Accessibility — all forms call .WithAccessible(console.IsAccessibleMode()). IsAccessibleMode() checks ACCESSIBLE, TERM=dumb, and NO_COLOR env vars.
• TTY detection — interactive forms guard behind tty.IsStderrTerminal() checks, with text-mode fallbacks for pipes/CI (showTextConfirm, showTextList).
• Field types used correctly:
  • huh.NewInput() with EchoModePassword for secrets (input.go)
  • huh.NewConfirm() for yes/no confirmations (confirm.go)
  • huh.NewSelect[string]() for interactive lists (list.go)
  • Multi-field group forms in add_interactive_*.go CLI commands
• Validation — input fields include Validate() callbacks (e.g., empty-string rejection for secrets).

Files using Huh

File	Fields
pkg/console/input.go	Input + EchoModePassword, validation
pkg/console/confirm.go	Confirm with text fallback
pkg/console/list.go	Select[string] with text fallback
pkg/styles/huh_theme.go	Theme definition
pkg/cli/interactive.go	Multi-field group forms
pkg/cli/add_interactive_auth.go	Auth flow forms
pkg/cli/add_interactive_git.go	Git config forms
pkg/cli/add_interactive_workflow.go	Workflow selection forms
pkg/cli/add_interactive_orchestrator.go	Orchestrator forms
pkg/cli/add_interactive_engine.go	Engine selection forms
pkg/cli/add_interactive_schedule.go	Schedule config forms
pkg/cli/engine_secrets.go	Secret input forms
pkg/cli/run_interactive.go	Run parameter forms

---

Console Output Patterns

✅ Package design

The pkg/console package follows a clean two-convention naming scheme documented in doc.go:

• Format* — pure string transforms (e.g., FormatSuccessMessage, FormatErrorMessage, FormatCommandMessage)
• Render* — structured/layout output (e.g., RenderTable, RenderTitleBox, RenderErrorBox, RenderTree)

Output routing is clearly defined: diagnostic output → stderr; structured data → stdout.

⚠️ Minor inconsistencies found

1. `trial_confirmation.go` — mixed formatting in execution steps list

Lines 182–183 use unstyled fmt.Fprintf(os.Stderr, ...) for sub-step labels, while adjacent lines use console.FormatInfoMessage():

// Styled:
fmt.Fprintf(os.Stderr, console.FormatInfoMessage("  %d. For each of %d executions:\n"), stepNum, opts.repeatCount+1)
// Unstyled sub-steps:
fmt.Fprintf(os.Stderr, "     a. Execute %s\n", workflowName)
fmt.Fprintf(os.Stderr, "     b. Auto-merge any pull requests created during execution\n")

The sub-step lines (a., b.) lack the console.FormatInfoMessage() wrapping, resulting in unstyled output mixed with styled parent steps.

Suggested fix: wrap the sub-step fmt.Fprintf calls with console.FormatInfoMessage().

2. `compile_stats.go` — unformatted error display

Several stderr writes use raw fmt.Fprintf with Unicode symbols instead of console formatters:

fmt.Fprintf(os.Stderr, "  ✗ %s\n", filepath.Base(failure.Path))
fmt.Fprintf(os.Stderr, "  i Suppressed %d cascading error(s)...\n", ...)

These bypass TTY detection and adaptive styling. console.FormatErrorMessage() or console.FormatInfoMessage() would be more consistent.

3. `vscode_config.go:82` — plain info message

fmt.Fprintf(os.Stderr, "Settings file already exists at %s\n", settingsPath)

This would benefit from console.FormatInfoMessage() or console.FormatWarningMessage() for consistency.

✅ Intentional raw fmt.Fprintf patterns (not issues)

• logs_format_compact.go (~100 stdout writes): Explicitly documented as "maximally information-dense output optimized for agentic consumption" — LLM-readable, flat, no decoration. Raw fmt.Fprintf(os.Stdout, ...) is correct here.
• audit_diff_render.go: Outputs Markdown/JSON to stdout for structured diff display — intentional machine-readable format.
• Internal strings.Builder use in trial_confirmation.go: fmt.Fprintf(&buf, ...) into buffers (not os.Stderr/os.Stdout) is correct for composing strings before passing to console.RenderInfoSection().

---

Recommendations

1. Wrap remaining bare sub-step lines in trial_confirmation.go with console.FormatInfoMessage() (lines 182–183 and similar) to restore visual consistency with parent steps.
2. Replace bare fmt.Fprintf(os.Stderr, ...) in compile_stats.go error display loops with console.FormatErrorMessage() / console.FormatInfoMessage() to get TTY-gated adaptive styling on the ✗ / i indicators.
3. Consider using console.FormatWarningMessage() for the existing-settings warning in vscode_config.go:82.
4. No changes needed to Lipgloss, Huh, or the styles package — these are consistently and correctly implemented throughout the codebase.

References:

• §27867364683

Generated by 💄 Terminal Stylist · 67.9 AIC · ⌖ 11.3 AIC · ⊞ 5.6K · ◷

• expires on Jun 21, 2026, 1:50 AM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-06-21T09:50:52.731Z.

Closed by Workflow