Skip to content

[deep-report] Use fmt.Fprint(os.Stdout, ...) instead of bare fmt.Print in status_command.go/view_command.go #55072

Description

@github-actions

Description

Terminal Stylist's console-output audit (discussion #55050) found 2 non-test .go files using bare fmt.Print instead of the explicit fmt.Fprint(os.Stdout, ...) pattern used by sibling calls in the same functions:

  • pkg/cli/status_command.go:295fmt.Print(console.RenderStruct(statuses)), while lines just above it in the same function use fmt.Fprintln(os.Stdout, ...) / fmt.Fprintln(os.Stderr, ...).
  • pkg/cli/view_command.go:168fmt.Print(output) where output := renderUnifiedTimelineStream(events), same inconsistency with neighboring fmt.Fprintln(os.Stderr, ...) calls.

Both already build styled content via pkg/console helpers; only the final print call bypasses explicit stream targeting. Behavior is unchanged (both already default to stdout) — this is a pure consistency fix.

Expected Impact

Minor polish: makes stream targeting explicit and consistent with the rest of pkg/cli's console-output conventions, removing the only 2 bare fmt.Print call sites outside test fixtures/doc comments.

Suggested Agent

New Agent (trivial mechanical fix).

Estimated Effort

Fast (< 30 min)

Data Source

DeepReport analysis, 2026-08-23 cycle, sourced from discussion #55050 (Terminal Stylist Report — Console Output Analysis).

Generated by 🔬 Deep Report · agent · 158 AIC · ⌖ 8.29 AIC · ⊞ 12.4K ·

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions