Repository navigation
[cli-consistency] CLI Consistency Issues - 2026-10-05 #65866
Description
Summary
Inspected 410 command/subcommand help files (from /tmp/gh-aw/agent/all-help.txt) and compared with docs/src/content/docs/setup/cli.md. Found 4 issues: 0 high, 2 medium, 2 low.
Documentation gaps
1. gh aw work-queue is undocumented in cli.md (medium)
- Help:
Experimental: inspect and update a Git-backed work queuewith subcommandscancel-claim, cancel-work, claim, compact, finish, replay, stats, submit-work. cli.mdhas nogh aw work-queuesection or command-table row (only a mention of thework-queueartifact set underaudit). Flags--branch,--claim-id,--work-id,--attempt-id,--outcome,--run-id,--fileappear nowhere in the doc.- Fix: add a command-table row and a section, as done for other experimental commands (
sessions,edit).
Flag inconsistencies
2. -l short flag means different things (medium)
gh aw trial:-l, --logical-repo string Repository to simulate workflow execution against (for trial mode)gh aw project new:-l, --link string Repository to link project to (format: owner/repo)- Expected: one meaning per short flag across commands. Fix: drop or change
-lfor one of them (e.g. leave--linklong-only).
3. work-queue flags don't follow the common conventions (low)
- Other commands:
-j, --json Output results in JSON formatand-r, --repo string Target repository ([HOST/]owner/repo format). Defaults to current repository. work-queue:--json Output JSONand--repo string GitHub repository owner/repo(no-j/-r, different wording, no default stated).- Fix: add
-j/-rand reuse the standard descriptions.
4. Inconsistent --repo description wording (low)
- Variants seen:
Target repository (owner/repo format only; GHES host prefixes are not supported),... Required unless --org is provided, and the standard[HOST/]owner/repotext. Some are intentional but the phrasing differs; consider a shared helper string.
Metadata
- Date: 2026-10-05; method: scripted scan of pre-collected help output for flags, short-flag collisions, typos, and doc coverage; run 37317266718.
Generated by ✅ CLI Consistency Checker · copilot · auto · 24.3 AIC · ⌖ 6.91 AIC · ⊞ 8.3K · ◷
- expires on Oct 7, 2026, 5:37 AM UTC-08:00
Activity
github-actions commentedon Oct 6, 2026
🍪 Issue Monster selected this for Copilot
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
github-actions commentedon Oct 6, 2026
🍪 Issue Monster selected this for Copilot
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
github-actions commentedon Oct 6, 2026
🍪 Issue Monster selected this for Copilot
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
github-actions commentedon Oct 6, 2026
Caution
agentic threat detected
Threat detection flagged this output in warn mode. Manual review is REQUIRED before any follow-up automation.
Details
Potential security threats were detected in the agent output.
Review the workflow run logs for details.
🍪 Issue Monster selected this for Copilot
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
github-actions commentedon Oct 6, 2026
🍪 Issue Monster selected this for Copilot
I identified this as a strong, self-contained candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, Copilot will analyze the issue and open a pull request with the fix.
Om nom nom! 🍪
github-actions commentedon Oct 6, 2026
🍪 Issue Monster selected this for Copilot
I identified this as a strong, self-contained candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, Copilot will analyze the issue and open a pull request with the fix.
Om nom nom! 🍪
github-actions commentedon Oct 7, 2026
Caution
agentic threat detected
Threat detection flagged this output in warn mode. Manual review is REQUIRED before any follow-up automation.
Details
Potential security threats were detected in the agent output.
Review the workflow run logs for details.
🍪 Issue Monster selected this for Copilot
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
github-actions commentedon Oct 7, 2026
🍪 Issue Monster selected this for Copilot
I have identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
github-actions commentedon Oct 7, 2026
This issue was automatically closed because it expired on 2026-10-07T13:37:43.577Z.