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

[github-actions[bot]]

This report summarizes the console output patterns found across 879 non-test Go source files in github/gh-aw, with focus on consistency, Lipgloss v2 usage, and Huh form implementations.

Key Metrics

Metric	Count
Total non-test Go files	879
Files using console.* formatters	~95 (pkg/cli)
console.Format* call sites	1,539
Raw fmt.Fprintf(os.Stderr, ...) (no formatter)	251
Files using Lipgloss directly	10
Files using Huh forms	3

---

Strengths ✅

1. Well-designed pkg/console package

The console package is the clear centerpiece of CLI output. It provides:

• TTY-aware rendering via applyStyle() — styles silently degrade when piped
• Rust-style compiler error rendering with source context and ^ pointers
• Adaptive colors via styles.LightDark() throughout pkg/styles
• RenderTable, RenderTitleBox, RenderErrorBox, RenderInfoSection, RenderComposedSections — rich layout utilities built on Lipgloss v2

2. Consistent console.Format* adoption

The most-used formatters show strong adoption:

Formatter	Calls
console.FormatInfoMessage	636
console.FormatWarningMessage	467
console.FormatSuccessMessage	211
console.FormatVerboseMessage	65
console.FormatErrorMessage	61
console.FormatCommandMessage	20
console.FormatProgressMessage	14

3. Lipgloss v2 best practices followed

• pkg/styles/theme.go uses compat.AdaptiveColor for all semantic colors, ensuring readability in both light/dark themes
• lipgloss.LightDark(isDark) is correctly used in HuhTheme to build all adaptive color values
• pkg/console/spinner.go uses Bubble Tea + charm.land/bubbles/v2/spinner for idiomatic animation
• pkg/cli/compile_schedule_calendar.go checks isTerminal before applying lipgloss.Style, then returns lipgloss.NewStyle() (no-op) for non-TTY
• pkg/cli/gateway_logs_timeline_render.go defines a streamStyleRenderer interface for rendering without direct lipgloss coupling in helpers

4. Huh forms with custom themed styles

Three files use charm.land/huh/v2 forms:

• add_interactive_workflow.go — Confirm dialog for workflow creation
• add_interactive_schedule.go — Select field for schedule frequency
• add_interactive_git.go — Select for merge actions

All leverage pkg/styles.HuhTheme, a full huh.ThemeFunc that maps the Dracula/adaptive palette to every Huh style state (Focused, Blurred, Group).

---

Areas for Improvement ⚠️

251 raw fmt.Fprintf(os.Stderr, ...) calls bypassing console formatters

The top offenders are:

File	Raw stderr calls
pkg/cli/mcp_inspect_mcp.go	37
pkg/cli/audit_report_render.go	20
pkg/cli/audit_cross_run_render.go	18
pkg/cli/compile_stats.go	14
pkg/cli/enable.go	12
pkg/cli/deps_report.go	12
pkg/cli/add_interactive_workflow.go	12
pkg/cli/experiments_analyze_statistics.go	11

Examples of output that should use console formatters:

// ❌ mcp_inspect_mcp.go — raw emojis, no styling adaptation
fmt.Fprintf(os.Stderr, "📋 **Name:** %s\n", foundTool.Name)
fmt.Fprintf(os.Stderr, "✅ **Status:** Allowed\n")
fmt.Fprintf(os.Stderr, "🚫 **Status:** Not allowed...\n")

// ✅ Preferred — uses console package, TTY-aware
fmt.Fprintln(os.Stderr, console.FormatInfoMessage("Name: "+foundTool.Name))
fmt.Fprintln(os.Stderr, console.FormatSuccessMessage("Status: Allowed"))
fmt.Fprintln(os.Stderr, console.FormatWarningMessage("Status: Not allowed (add to 'allowed' list in workflow frontmatter)"))

// ❌ audit_report_render.go — mixed manual formatting
fmt.Fprintf(os.Stderr, "  tokens: in=%s out=%s cache_read=%s reqs=%d\n", ...)

// ✅ Preferred — use FormatVerboseMessage for structured debug details
fmt.Fprintln(os.Stderr, console.FormatVerboseMessage(fmt.Sprintf("tokens: in=%s out=%s ...", ...)))

// ❌ add_interactive_workflow.go — plain debug traces
fmt.Fprintf(os.Stderr, "Checking workflow status (attempt %d/5) for: %s\n", i+1, workflowName)

// ✅ Preferred — use the logger package for debug/trace output
log.Printf("Checking workflow status (attempt %d/5) for: %s", i+1, workflowName)

Inline debug traces should use pkg/logger, not fmt.Fprintf

Several files in add_interactive_workflow.go emit diagnostic traces unconditionally:

fmt.Fprintf(os.Stderr, "Running: gh %s\n", strings.Join(args, " "))
fmt.Fprintf(os.Stderr, "gh workflow list failed: %v\n", err)
fmt.Fprintf(os.Stderr, "gh workflow list output: %s\n", string(output))
fmt.Fprintf(os.Stderr, "Workflow with filename '%s' found in workflow list\n", pattern)

These should use logger.New("cli:add_interactive_workflow") so they are gated behind DEBUG=cli:* and don't pollute normal output.

Markdown bold syntax in raw stderr output (mcp_inspect_mcp.go)

Several lines embed Markdown bold syntax (**Name:**) that renders as literal asterisks in terminals. Since the output targets stderr (a terminal stream), Lipgloss bold styling is the correct approach:

// ❌ Current
fmt.Fprintf(os.Stderr, "📄 **Title:** %s\n", foundTool.Title)

// ✅ Preferred
label := lipgloss.NewStyle().Bold(true).Render("Title:")
fmt.Fprintf(os.Stderr, "%s %s\n", label, foundTool.Title)
// OR use console.FormatSectionHeader for structural labels

Minor: compile_schedule_calendar.go direct Lipgloss calls vs. console package

compile_schedule_calendar.go correctly gates styles with isTerminal, but writes directly to stderr via fmt.Fprintln(os.Stderr, row.String()) rather than routing through the console package. Since the calendar render is bespoke (grid layout), this is defensible — but extracting it into a console.RenderCalendar() helper would improve testability and centralize TTY logic.

---

Recommendations

1. Migrate mcp_inspect_mcp.go — Replace 37 raw fmt.Fprintf calls with console.Format* equivalents. The tool inspection output uses emojis and Markdown bold that should be proper Lipgloss styles.

2. Adopt pkg/logger for debug traces in add_interactive_workflow.go — The 12 raw debug writes are unconditionally visible to users; they should be DEBUG=cli:*-gated.

3. Audit audit_report_render.go and audit_cross_run_render.go — These render structured run data inline; adopting console.FormatVerboseMessage or console.RenderTable where appropriate would improve visual consistency.

4. Consider console.FormatListItem — Only 3 usages found. Manual bullet " • " strings appear in several files that could use this formatter.

5. Continue using HuhTheme — The custom huh theme is excellent. All three Huh-using files already use it correctly with huh.NewForm(...).WithTheme(styles.HuhTheme).

References: §26878171779

Generated by 💄 Terminal Stylist · sonnet46 1.5M · ◷

• expires on Jun 4, 2026, 10:18 AM UTC

[github-actions[bot]]

💥 WHOOSH! The Smoke Test Agent BURST onto the scene! 🦸

KA-POW! 💢 All systems checked — Claude engine running at full power! The Agent zoomed through MCP servers, leapt over build steps, and landed a perfect snapshot! 🎯

"This discussion has been officially smoke-tested!" — THE END... or IS it?! 📖✨

Warning

Firewall blocked 6 domains

The following domains were blocked by the firewall during workflow execution:

• accounts.google.com
• android.clients.google.com
• clients2.google.com
• contentautofill.googleapis.com
• safebrowsingohttpgateway.googleapis.com
• www.google.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "accounts.google.com"
    - "android.clients.google.com"
    - "clients2.google.com"
    - "contentautofill.googleapis.com"
    - "safebrowsingohttpgateway.googleapis.com"
    - "www.google.com"

See Network Configuration for more information.

💥 [THE END] — Illustrated by Smoke Claude · opus48 5.1M · ◷

[github-actions[bot]]

Smoke-test sprite was here: buttons booped, logs sniffed, sparkles deployed. ✨🤖

Warning

Firewall blocked 6 domains

The following domains were blocked by the firewall during workflow execution:

• accounts.google.com
• android.clients.google.com
• clients2.google.com
• contentautofill.googleapis.com
• safebrowsingohttpgateway.googleapis.com
• www.google.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "accounts.google.com"
    - "android.clients.google.com"
    - "clients2.google.com"
    - "contentautofill.googleapis.com"
    - "safebrowsingohttpgateway.googleapis.com"
    - "www.google.com"

See Network Configuration for more information.

📰 BREAKING: Report filed by Smoke Copilot · gpt54 8.8M · ◷