fix DFanso#52 : add Groq LLM support to setup and generation

[adeeshperera]

• Add Groq to LLM provider selection in setup
• Import groq package and add case in commit message generation
• Include Groq-specific error handling

Summary by CodeRabbit

• New Features
  • Added Groq as a selectable LLM provider in the CLI.
  • Commit message generation now supports Groq alongside existing providers (OpenAI, Claude, Gemini, Grok, Ollama).
  • Provider selection flow updated to include Groq in the available options.

[coderabbitai]

Walkthrough

Adds Groq as a selectable LLM provider in the CLI. Updates the provider setup list and integrates Groq into the commit message generation switch alongside existing providers. No other logic, API shapes, or exported entities are modified.

Changes

Cohort / File(s)	Summary of changes
CLI LLM integration cmd/cli/createMsg.go, cmd/cli/llmSetup.go	Added Groq to the LLM providers list and switch handling for commit message generation and related error prompts. No other behavioral changes observed.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    actor User
    participant CLI as CLI (createMsg)
    participant LLM as LLM Provider
    note over CLI: User selects provider (OpenAI/Claude/Gemini/Grok/Ollama/Groq)

    User ->> CLI: Generate commit message
    CLI ->> CLI: Switch on selected provider
    alt Provider = Groq
        CLI ->> LLM: Send prompt (Groq)
        LLM -->> CLI: Commit message text
    else Other providers
        CLI ->> LLM: Send prompt (selected LLM)
        LLM -->> CLI: Commit message text
    end
    CLI -->> User: Output commit message
    note over CLI: Standard error handling unchanged

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• feat: add Groq as free LLM provider #45: Introduces Groq as an LLM provider and wires it into CLI selection, mirroring this integration.

Suggested labels

enhancement, go

Suggested reviewers

• DFanso

Poem

I thump my paw—new wires hum,
A Groq-hop joins our clever scrum.
Switch-case burrows, tidy and neat,
Commit words sprout—concise, complete.
Carrot-shaped prompts? Crunchy delight.
Ship it quick—ears up, code tight! 🥕🐇

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title clearly summarizes the main change by stating the addition of Groq LLM support to both setup and message generation, directly reflecting the pull request’s objectives without using vague terminology or unnecessary details.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

cmd/cli/createMsg.go (1)

114-132: Consider making "Grok" case explicit in the switch.

The switch statement uses a default case to handle "Grok", while all other providers (including the newly added Groq) have explicit cases. This creates an inconsistency, especially since the error handling switch (lines 137-150) has an explicit "Grok" case.

For consistency and clarity, consider refactoring to make "Grok" an explicit case:

 	case "Groq":
 		commitMsg, err = groq.GenerateCommitMessage(config, changes, apiKey)
 	case "Ollama":
 		model := "llama3:latest"
 		
 		commitMsg, err = ollama.GenerateCommitMessage(config, changes, apiKey, model)
+	case "Grok":
+		commitMsg, err = grok.GenerateCommitMessage(config, changes, apiKey)
 	default:
-		commitMsg, err = grok.GenerateCommitMessage(config, changes, apiKey)
+		spinnerGenerating.Fail("Unsupported LLM provider")
+		pterm.Error.Printf("Unsupported LLM provider: %s\n", commitLLM)
+		os.Exit(1)
 	}

This makes the code more maintainable and catches potential configuration errors where an unsupported provider name is used.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2a2bf89 and 12bdb45.

📒 Files selected for processing (2)

• cmd/cli/createMsg.go (3 hunks)
• cmd/cli/llmSetup.go (1 hunks)

🧰 Additional context used

🧬 Code graph analysis (1)

cmd/cli/createMsg.go (1)

internal/groq/groq.go (3)

• GenerateCommitMessage (46-111)
• Message (27-29)
• Role (15-18)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Build Go Binary (windows-latest)

🔇 Additional comments (4)

cmd/cli/llmSetup.go (1)

14-14: LGTM! Groq added to provider list.

The addition of "Groq" to the LLM providers list is correct and follows the existing pattern. Groq will use the standard API key prompt flow, which is appropriate for this provider.

cmd/cli/createMsg.go (3)

14-14: LGTM! Groq package imported.

The import statement correctly adds the Groq package following the existing import pattern.

---

124-125: LGTM! Groq case added to generation switch.

The Groq case correctly follows the same pattern as other LLM providers, calling groq.GenerateCommitMessage with the appropriate parameters.

---

144-145: LGTM! Groq error handling added.

The Groq error case is properly integrated into the error handling switch, maintaining consistency with other providers.

[DFanso]

Approved 🎉