No changes needed: enable/disable commands already use correct capitalization

[Copilot]

Investigation confirms the reported capitalization inconsistency does not exist. Both enable and disable commands already use lowercase "agentic workflows" per the guidelines in specs/capitalization.md.

Current State (Already Correct)

cmd/gh-aw/main.go:

var enableCmd = &cobra.Command{
    Short: "Enable agentic workflows",  // ✓ lowercase "agentic"
}

var disableCmd = &cobra.Command{
    Short: "Disable agentic workflows and cancel any in-progress runs",  // ✓ lowercase "agentic"
}

Verification

• Source code inspection: Both commands use lowercase "agentic"
• Test suite: TestCapitalizationConsistency passes
• Runtime verification: Help text displays correctly
• Spec compliance: Matches specs/capitalization.md guidelines for generic workflow references

The issue appears to have been auto-generated with incorrect categorization. No code changes required.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[cli-consistency] Inconsistent capitalization of 'agentic workflows' in enable/disable commands</issue_title>
<issue_description>## Issue Description

Type: Inconsistency in command capitalization
Priority: Low

Current State

The CLI commands have inconsistent capitalization in their Short descriptions when referring to "agentic workflows" or similar terms.

Evidence from Source Code

Commands using lowercase "agentic workflows":

• init_command.go (line 17): "Initialize repository for agentic workflows"
• add_command.go (line 23): "Add agentic workflows from repositories to .github/workflows"
• trial_command.go (line 45): "Trial one or more agentic workflows as if..."
• fix_command.go (line 34): "Apply automatic codemod-style fixes to agentic workflow files"
• update_command.go (line 17): "Update agentic workflows from their source repositories..."
• logs_command.go (line 27): "Download and analyze agentic workflow logs..."
• status.go (line 12): "Show status of all agentic workflows in the repository"
• mcp_add.go (line 306): "Add an MCP tool to an agentic workflow"
• mcp_list.go (line 224): "List MCP servers defined in agentic workflows"

Commands using capitalized terms:

• enable_cmd (main.go line 132): "Enable agentic workflows"
• disable_cmd (main.go line 151): "Disable agentic workflows and cancel..."

Issue

The product name "GitHub Agentic Workflows" should be consistently capitalized according to the capitalization guidelines in specs/capitalization.md which states:

Product Name: "GitHub Agentic Workflows" (always capitalize)
Feature Names: Use sentence case (e.g., "safe output messages")

When referring to the workflows themselves (not the product), it appears the codebase uses lowercase "agentic workflows" in most places, but enable and disable commands use this as if it were part of the product name.

Actual Impact

Minor inconsistency in CLI help text. Users may perceive this as lack of polish.

Expected Behavior

Consistent capitalization throughout. Since these are referring to workflow artifacts (not the product itself), they should use lowercase: "agentic workflows"

Suggested Fix

Update the Short descriptions in main.go:

• Line 132: "Enable agentic workflows" (lowercase 'agentic')
• Line 151: "Disable agentic workflows and cancel..." (lowercase 'agentic')

This matches the pattern used in all other command descriptions.

AI generated by CLI Consistency Checker

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

• Fixes [cli-consistency] Inconsistent capitalization of 'agentic workflows' in enable/disable commands #6960

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.