Skip to content

Agent UX: pm comments should accept --body as an alias for --add (gh/glab muscle memory) #498

Closed

Description

@unbraind

Problem

pm comments <id> --body "..." fails with Unknown option --body.

Agents (and humans) coming from gh issue comment --body, gh pr comment --body, and glab reach for --body reflexively — it is the de-facto standard flag name for comment text across the CLIs agents use most. Today that costs every agent one failed invocation + one --help round-trip (~2 wasted tool calls and a few hundred tokens) before landing on --add.

Observed in a real session today: first attempt used --body, failed, required pm comment --help to discover --add.

Suggestion

Accept --body <text> as a hidden alias for --add <text> on pm comments (and anywhere else comment text is taken, e.g. --edit replacement text). Alternatively (or additionally), make the error message suggest the correct flag: Unknown option --body — did you mean --add? — the existing unknown-command suggestion machinery could cover unknown options too.

Why it matters (project management = context management)

Tiny per-call friction, but comments are one of the highest-frequency write paths for agent workflows (progress logging is core to pm dogfooding). Alias costs nothing, saves a failed call + help lookup per fresh agent session.

Filed from ecosystem dogfooding; no local customization involved — vanilla @unbrained/pm-cli 2026.7.10.

Activity

  1. coderabbitai commented on Jul 10, 2026

    @coderabbitai
    🔗 Related PRs

    #230 - Single-call mutation ergonomics: pm create/update --body-file, pm close -m/-r/-d, --resolution as close reason [closed]
    #255 - CLI surface correctness & agent ergonomics: get body parity, type-error path, comment edit/delete, validate dup-codes (GH-252/253/243/235) [closed]
    #475 - Improve package install and annotation agent UX [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. added a commit that references this issue on Jul 10, 2026
  3. unbraind commented on Jul 10, 2026

    @unbraind
    OwnerAuthor

    Fixed and merged in PR #502 at main commit 6ad4f23. The full bundle passed 100/100/100/100 coverage (5,528 tests), packed smoke, 88-command dogfood, Windows/CodeQL/Trivy/Semgrep/static/typecheck/compatibility gates, and AI review follow-ups.

  4. unbraind commented on Jul 11, 2026

    @unbraind
    OwnerAuthor

    pm tracker item:

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions