Fix trial command parameter placeholder: use workflow-spec

[Copilot]

The trial command used <workflow> as its parameter placeholder, inconsistent with other commands using [workflow-id], [workflow-id-or-file], or <workflow-id>.

Changes

• Updated trial command Use field to <workflow-spec> to reflect that it accepts multiple specification formats:
  • Repository paths: githubnext/agentics/weekly-research
  • Local files: ./local-workflow.md
  • GitHub URLs

// Before
Use: "trial <workflow>...",

// After
Use: "trial <workflow-spec>...",

This aligns with similar flexible commands like MCP commands that use [workflow-id-or-file].

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/user
  • Triggering command: /usr/bin/gh gh api user --jq .login .git/shallow.lock GO111MODULE .cfg GOINSECURE rvmoqczp GOMODCACHE 4331031/b332/fileutil.test e=/t�� it/ref/tags/v5 GO111MODULE "CURL_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt", "REQUESTS_CA_Bxterm-color GOINSECURE GOMOD GOMODCACHE ache/go/1.25.0/x64/pkg/tool/linux_amd64/link (http block)
  • Triggering command: /usr/bin/gh gh api user --jq .login -dotnet.git GO111MODULE e/git GOINSECURE GOMOD GOMODCACHE e/git env tags/93cb6efe18208431cddfb8368fd83d5badbf9bfd om/org1/repo1 /opt/hostedtoolcache/go/1.25.0/x64/bin/go GOINSECURE GOMOD GOMODCACHE go (http block)
  • Triggering command: /usr/bin/gh gh api user --jq .login 4331031/b341/gateway.test -d/gh-aw 6e3179860e28cde6dd73315e4c835e32ff3/log.json GOINSECURE GOMOD GOMODCACHE ro_gIqygTCewh/DLwwJ0Zi7nUOmbyeNqW7/HIMdtutUag6Hg7fyHDlp/I58Tj8Ur--jq 1/x6�� runs/20251208-182219-17291/test-2437756014 k/gh-aw/gh-aw/cmd/gh-aw/capitalization_test.go runs/20251208-182219-17291/test-2437756014/.gitattributes GOINSECURE GOMOD GOMODCACHE /opt/hostedtoolc-address (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[cli-consistency] Inconsistent placeholder: trial command uses <workflow> instead of <workflow-id></issue_title>
<issue_description>## Issue Description

Command: gh aw trial
Type: Inconsistent parameter naming
Priority: Low

Current Behavior

The trial command uses (workflow) as the parameter placeholder:

From trial_command.go line 44:

cmd := &cobra.Command{
    Use:   "trial (workflow)...",  // ← Uses "workflow"
    Short: "Trial one or more agentic workflows as if they were running in a repository",
    // ...
}

Issue

All other commands that accept workflow identifiers use consistent naming:

• Most common: [workflow-id] - used by enable, disable, update, status, new, etc.
• Alternative: [workflow-id-or-file] - used by MCP commands for more flexibility
• Run command: (workflow-id) (required parameter)

The trial command is the only one using just (workflow) which breaks the pattern.

Why This Matters

Looking at the examples in the trial command, it accepts workflow specifications like:

• githubnext/agentics/weekly-research (repository/workflow format)
• ./local-workflow.md (file path)

So it's more than just a workflow-id, but it should still follow the naming convention used by other commands.

Suggested Fix

Option 1 (Best for consistency):

Use:   "trial (workflow-spec)...",

Option 2 (Match existing patterns):

Use:   "trial (workflow-id-or-spec)...",

The first option is cleaner and the Long description already explains what workflow specifications are accepted.

AI generated by CLI Consistency Checker

Comments on the Issue (you are @copilot in this section)

• Fixes [cli-consistency] Inconsistent placeholder: trial command uses &lt;workflow&gt; instead of &lt;workflow-id&gt; #5856

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.