Skip to content

Chore: CLI prompts for consistency and standardize error messages #225

Description

@codxbrexx

Summary

The CLI currently uses inconsistent punctuation, capitalization, and prompt wording across errors, questions, and status output.
This does not break functionality, but it makes the interface feel less polished and harder to scan quickly.

File Evidence

  • deploy/TODO.md: already calls out the need to make error messages and input requests uniform.
  • message strings are spread across files such as:
    • deploy/src/auth.ts
    • deploy/src/help.ts
    • deploy/src/plan.ts
    • deploy/src/utils.ts
    • deploy/src/cli/messages.ts
    • deploy/src/cli/inputs.ts
    • deploy/src/cli/selection.ts

Examples

  • Some prompts end with :, while others do not.
  • Some errors end with punctuation, others do not.
  • Similar user-facing actions use different wording.

Expected Behavior

CLI output should follow a consistent style for:

  • prompts
  • confirmations
  • success messages
  • warnings
  • errors

Actual Behavior

User-facing text is inconsistent across deploy, even for similar flows.

Scope

  • Standardize punctuation, capitalization, spelling, and prompt phrasing.
  • Keep exit codes, routing, JSON output, and command behavior unchanged.

Proposed Fix

  • Define a simple style guide for CLI copy.
  • Standardize prompt endings, sentence punctuation, and tone.
  • Apply the style pass across all user-facing strings without changing command behavior.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions