Repository navigation
Update llm instructions for argo - #770
Conversation
WalkthroughThe ArgoCD toolset instructions were updated to include explicit directives for always checking application health status and retrieving diffs for out-of-sync resources. The step list was expanded to mandate these actions as part of the diagnostic process, with clarifications added to distinguish these steps from general investigation procedures. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
holmes/plugins/toolsets/argocd.yaml (2)
9-10: Standardize ArgoCD capitalization & trim minor wording friction
Minor stylistic inconsistencies ( “argo cd” / extra comma ) can distract or confuse when the text is rendered.- IMPORTANT: If you are asked about health issues, ALWAYS check if the argo cd apps are in a healthy state. - If some resource is out of sync, ALWAYS show the diff, using the argocd_app_diff tool, between the desired state and the current state. + IMPORTANT: If you are asked about health issues, ALWAYS check if the ArgoCD applications are in a healthy state. + If any resource is out of sync, ALWAYS show the diff between the desired and current state using the argocd_app_diff tool.
12-18: Tighten phrasing to avoid redundancy (“ALWAYS … as well”)
The current sentence repeats the “ALWAYS” emphasis and reads a bit clunky. A lighter wording keeps the directive clear:- In addition to the general investigation steps, ALWAYS follow these steps as well: + In addition to the general investigation steps, ALSO perform the following mandatory steps:Optional but improves readability.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
holmes/plugins/toolsets/argocd.yaml(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
holmes/plugins/toolsets/**/*.yaml
📄 CodeRabbit Inference Engine (CLAUDE.md)
holmes/plugins/toolsets/**/*.yaml: Toolsets: holmes/plugins/toolsets/{name}.yaml or {name}/
Bash toolset validates commands for safety
Files:
holmes/plugins/toolsets/argocd.yaml
🧠 Learnings (2)
📚 Learning: applies to holmes/plugins/toolsets/**/*.yaml : toolsets: holmes/plugins/toolsets/{name}.yaml or {nam...
Learnt from: CR
PR: robusta-dev/holmesgpt#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-27T14:10:31.590Z
Learning: Applies to holmes/plugins/toolsets/**/*.yaml : Toolsets: holmes/plugins/toolsets/{name}.yaml or {name}/
Applied to files:
holmes/plugins/toolsets/argocd.yaml
📚 Learning: applies to holmes/plugins/toolsets/**/*.yaml : bash toolset validates commands for safety...
Learnt from: CR
PR: robusta-dev/holmesgpt#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-27T14:10:31.590Z
Learning: Applies to holmes/plugins/toolsets/**/*.yaml : Bash toolset validates commands for safety
Applied to files:
holmes/plugins/toolsets/argocd.yaml
⏰ 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). (3)
- GitHub Check: llm_evals
- GitHub Check: Pre-commit checks
- GitHub Check: Pre-commit checks
No description provided.