[terminal-stylist] Console output audit for gh-aw

[github-actions[bot]]

Summary

The repo already has a strong terminal presentation layer. pkg/console provides TTY-aware message formatting, accessibility-aware rendering, themed huh forms, and spinner/progress components, and the interactive CLI flows are using them in the right places.

What is working well

• pkg/logger/logger.go uses lipgloss and adaptive colors for debug output, with DEBUG/ACTIONS_RUNNER_DEBUG gating and stderr-safe logging.
• Interactive prompts in pkg/cli/run_interactive.go, pkg/cli/add_interactive_git.go, pkg/cli/add_interactive_auth.go, and related files consistently use console.NewSelectForm, console.NewInputForm, and console.NewConfirmForm rather than ad-hoc prompts.
• pkg/console already handles non-TTY fallback behavior, ANSI degradation, and accessible mode, which aligns well with the Charmbracelet ecosystem guidance.

Remaining gaps

• The CLI entrypoints still contain raw fmt.Fprintf/fmt.Fprintln output in places such as cmd/gh-aw/main.go for version/help paths and pkg/cli/run_interactive.go for non-TTY menu text. These are functional, but they bypass the repo’s styling conventions and make the UX less consistent.
• Some interactive flows still print hand-built bullet lists or manual instructions directly to stderr. Examples include the secret-manual steps in pkg/cli/add_interactive_git.go and the text-selection prompt in pkg/cli/run_interactive.go. These would benefit from section/list helpers or a dedicated console rendering helper.
• Internal helper tools under internal/tools and the standalone lint script in scripts/ use plain fmt output for basic CLI help and status lines. Those are lower priority, but they would still benefit from a common style wrapper if the project wants a single terminal UX standard.

Recommended next steps

1. Standardize remaining CLI entrypoint output in cmd/gh-aw/main.go around console.Format* helpers instead of raw fmt writes.
2. Replace hand-built text lists in interactive flows with console section/list helpers where possible, while preserving the existing non-TTY fallback behavior.
3. Add a lightweight guard (for example, a grep-based lint or unit-test expectation) so new fmt.Fprint* calls on stderr/stdout outside pkg/console are easier to spot.

Bottom line

The console experience is already strong, especially for interactive flows and debug logging. The main opportunity is to reduce the remaining hand-rolled text output so the CLI feels more uniform and easier to maintain.

Generated by 💄 Terminal Stylist · codex · mai10 · 10.9 AIC · ⌖ 1.18 AIC · ⊞ 13.4K · ◷

• expires on Aug 26, 2026, 1:00 AM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-08-26T09:00:12.192Z.

Closed by Workflow