Skip to content

Conversation

jerop
Copy link
Contributor

@jerop jerop commented Sep 18, 2025

Adds a security warning to all Gemini CLI workflow prompts, instructing the model to avoid using command substitution features like $(...), <(...), or >(...) in shell commands.

This is a preventative measure to avoid errors where the Gemini CLI rejects commands that use command substitution for security reasons. This change makes the security constraints of the tool explicit to the model.

Adds a security warning to all Gemini CLI workflow prompts, instructing the model to avoid using command substitution features like `$(...)`, `<(...)`, or `>(...)` in shell commands.

This is a preventative measure to avoid errors where the Gemini CLI rejects commands that use command substitution for security reasons. This change makes the security constraints of the tool explicit to the model.
Copy link

gemini-cli bot commented Sep 18, 2025

🤖 Hi @jerop, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

Copy link

gemini-cli bot commented Sep 18, 2025

🤖 I'm sorry @jerop, but I was unable to process your request. Please see the logs for more details.

Copy link

gemini-cli bot commented Sep 18, 2025

🤖 Hi @jerop, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

Copy link

@gemini-cli gemini-cli bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📋 Review Summary

This pull request enhances security by explicitly instructing the model to avoid command substitution in shell commands. The change is applied consistently across all relevant workflow files. The overall quality of the change is good.

🔍 General Feedback

  • The security warning is a good preventative measure and is well-articulated.
  • The change is consistently applied across all relevant files.
  • There is a minor stylistic inconsistency in the formatting of the new rule across different files (e.g., numbered lists, bullet points, and <rule> tags). While this doesn't affect the functionality, you might consider unifying the style in a future refactoring for better maintainability.

@jerop jerop linked an issue Sep 18, 2025 that may be closed by this pull request
@jerop jerop merged commit 65211e7 into main Sep 18, 2025
64 of 65 checks passed
@jerop jerop deleted the feat/add-security-warning-to-workflows branch September 18, 2025 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Command substitution using $(), <(), or >() is not allowed
2 participants