[terminal-stylist] Terminal Stylist Analysis — Console Output Patterns

[github-actions[bot]]

Overview

This report analyzes console output patterns across 752 Go source files in the github/gh-aw codebase. The project has a well-structured terminal output system built on Lipgloss v2 (charm.land/lipgloss/v2) and Huh v2 (charm.land/huh/v2), with a centralized pkg/console package providing format helpers.

Key numbers:

• 752 non-test Go source files scanned
• ~2,075 fmt.Fprintln(os.Stderr, ...) calls in pkg/cli/
• ~1,487 console.Format* calls (72% of stderr calls properly formatted)
• 367 raw stderr calls without console formatters (28% — improvement opportunity)
• 9 files using huh forms in pkg/cli/, all consistently themed

---

Lipgloss Usage

✅ What is Working Well

Adaptive colors throughout — pkg/styles/theme.go defines all colors as compat.AdaptiveColor{Light: ..., Dark: ...} using the Dracula-inspired palette. Every color constant has both a light and dark variant, ensuring readability on any terminal background.

TTY detection before applying styles — pkg/console/console.go gates all styling via applyStyle(), which checks tty.IsStdoutTerminal() before rendering Lipgloss styles. This prevents ANSI codes from leaking into pipes and redirects.

Diverse layout primitives in pkg/console/console.go:

• RenderTable() — uses charm.land/lipgloss/v2/table with alternating row colors, a styled header, and a total row
• RenderTitleBox() — double-border box with centered bold title (falls back to ━ separators)
• RenderErrorBox() — rounded border with error foreground color
• RenderInfoSection() — left-border emphasis block
• RenderComposedSections() — lipgloss.JoinVertical composition for stderr output

Rich set of message formatters — FormatSuccessMessage, FormatErrorMessage, FormatWarningMessage, FormatInfoMessage, FormatCommandMessage, FormatProgressMessage, FormatPromptMessage, FormatVerboseMessage, FormatListItem, FormatErrorChain — all consistently prefixed with semantic icons (✓, ✗, ⚠, i, ⚡, 🔨, ❓, 🔍).

Calendar heatmap with intensity styles — pkg/cli/compile_schedule_calendar.go uses per-cell Lipgloss styles scaling from ColorComment → ColorInfo → ColorSuccess → ColorWarning → ColorError to visualize density.

⚠️ Improvement Opportunities

367 raw fmt.Fprintln(os.Stderr, ...) without console formatting, mostly in:

• pkg/cli/deps_security.go (lines 97, 99, 121, 128) — blank lines and raw line variable output
• pkg/cli/compile_file_operations.go:113 — fmt.Fprintln(os.Stderr, err.Error()) should use console.FormatErrorMessage
• pkg/cli/compile_file_operations.go:213 — raw "Watching for file changes" string
• pkg/cli/copilot_setup.go:269–285 — multi-line YAML code block (could use console.RenderInfoSection)

audit_cross_run_render.go uses Markdown h1/h2 headers to stdout — correct for piped output per Unix conventions, but header levels should use ###+ per the project's report structure guidelines.

FormatLocationMessage and FormatCountMessage only exist in the WASM stub — pkg/console/console_wasm.go defines these two functions but there is no corresponding implementation in pkg/console/console.go for native builds. If ever called from CLI code, a build failure would result.

---

Huh Forms Usage

✅ What is Working Well

Consistent theming — All 9 files using huh.NewForm() call .WithTheme(styles.HuhTheme).WithAccessible(console.IsAccessibleMode()). The custom HuhTheme in pkg/styles/huh_theme.go maps the Dracula palette to all field states (focused, blurred, selected, error indicators, buttons, text inputs).

Accessibility mode — pkg/console/accessibility.go correctly detects ACCESSIBLE, TERM=dumb, and NO_COLOR and passes results to every form.

Proper field types — password inputs use EchoMode(huh.EchoModePassword), confirmations use huh.NewConfirm(), selections use huh.NewSelect[T](), free-form inputs use huh.NewInput().

Validation on inputs — interactive fields include .Validate() with descriptive error messages.

Centralized wrappers — pkg/console/confirm.go, list.go, and input.go provide single-field helpers that apply theme and accessibility, reducing boilerplate.

⚠️ Improvement Opportunities

Some fields lack .Description() text — in pkg/cli/interactive.go (lines 95, 170) some fields don't have explicit .Description(), reducing context for accessibility mode users.

RunWithContext inconsistency — some forms use .Run() and others .RunWithContext(ctx). Prefer .RunWithContext uniformly to respect cancellation signals.

---

Summary Table

Area	Status	Details
Adaptive colors	✅ Excellent	All colors use compat.AdaptiveColor with light/dark variants
TTY detection	✅ Excellent	applyStyle() gates all Lipgloss rendering
Table formatting	✅ Excellent	lipgloss/table with styled headers, alternating rows
Error formatting	✅ Good	FormatErrorChain handles wrapped errors with indentation
Huh theming	✅ Excellent	All form files apply HuhTheme + IsAccessibleMode()
Accessibility	✅ Good	NO_COLOR, TERM=dumb, ACCESSIBLE all detected
Raw stderr output	⚠️ Fair	367 unformatted calls — mostly blanks/spacing, a few messages
WASM/native parity	⚠️ Gap	FormatCountMessage/FormatLocationMessage missing from native
Form descriptions	⚠️ Minor	Some fields lack .Description() for accessibility context
audit_cross_run_render headers	i️ Note	Markdown h1/h2 in stdout — correct for pipes but inconsistent with report guidelines

---

Top Recommendations

1. Fix compile_file_operations.go:113 — replace fmt.Fprintln(os.Stderr, err.Error()) with fmt.Fprintln(os.Stderr, console.FormatErrorMessage(err.Error())).

2. Add FormatCountMessage / FormatLocationMessage to pkg/console/console.go so these functions exist for native builds and match the WASM stub signatures.

3. Standardize blank-line output — replace fmt.Fprintln(os.Stderr, "") with fmt.Fprintln(os.Stderr) (no string arg) for clarity.

4. Prefer .RunWithContext(ctx) over bare .Run() in all huh forms.

5. Add .Description() to form fields in pkg/cli/interactive.go for better accessibility mode experience.

References:

• Workflow run §25275026993

Generated by Terminal Stylist · ● 1.4M · ◷

• expires on May 4, 2026, 9:12 AM UTC

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-05-04T09:12:58.755Z.

Closed by Workflow