[cli-consistency] Status command lacks --repo flag unlike enable/disable commands

[github-actions]

Issue Description

Command: gh aw status
Type: Missing flag for consistency
Priority: Medium

Current Output (from pkg/cli/status.go, lines 24-44)

The status command shows the status of workflows but does not accept a --repo flag to check workflows in a different repository.

cmd.Flags().String("ref", "", "Filter runs by branch or tag name (e.g., main, v1.0.0)")
cmd.Flags().String("label", "", "Filter workflows by label")

Issue

The enable and disable commands (cmd/gh-aw/main.go, lines 493-494) both support a --repo flag:

enableCmd.Flags().StringP("repo", "r", "", "Target repository (owner/repo format). Defaults to current repository")
disableCmd.Flags().StringP("repo", "r", "", "Target repository (owner/repo format). Defaults to current repository")

This creates an inconsistent user experience where users can enable/disable workflows in other repositories but cannot check their status.

Suggested Fix

Add a --repo flag to the status command for consistency:

cmd.Flags().StringP("repo", "r", "", "Target repository (owner/repo format). Defaults to current repository")

Update the help text to include an example:

Examples:
  gh aw status                          # Show all workflow status
  gh aw status ci-                      # Show workflows with 'ci-' in name
  gh aw status --repo owner/other-repo  # Check status in different repository

This would make the workflow management commands (status, enable, disable) consistent in their ability to operate across repositories.

AI generated by CLI Consistency Checker