// Use when the user asks for feedback on code, a self-review, testing suggestions, or a sanity check. Provides structured feedback, test ideas, or a short review checklist so the user can validate their work.
| name | omega-feedback-test |
| description | Use when the user asks for feedback on code, a self-review, testing suggestions, or a sanity check. Provides structured feedback, test ideas, or a short review checklist so the user can validate their work. |
This skill follows the Agent Skills open standard and is discovered by Gemini CLI from Workspace Skills (.gemini/skills/). When the user wants feedback, testing suggestions, or a self-review while working in Gemini CLI, follow this workflow so they get consistent, actionable output.
Provide a short, scannable response:
Keep each section brief. If the user only asked for “test ideas”, focus there and shorten the rest.
When the user asks for tests or “how to test”:
This skill helps Gemini CLI act as a consistent “feedback and test” partner without changing how the rest of the session works.
Use when the user wants to use Google Gemini for analysis, large files or codebases, sandbox execution, or brainstorming. Uses headless Gemini CLI scripts (no MCP). Triggers on "use Gemini", "analyze with Gemini", "large file", "sandbox", "brainstorm with Gemini".
Use when the user wants to use Google Gemini for analysis, large files or codebases, sandbox execution, or brainstorming. Runs headless Gemini CLI via a Node script (no MCP). Triggers on "use Gemini", "ask Gemini", "analyze with Gemini", "large file", "sandbox", "brainstorm with Gemini".
Use when the user wants to use Google Gemini for analysis, large files or codebases, sandbox execution, or brainstorming. Runs headless Gemini CLI via a Node script (no MCP). Triggers on "use Gemini", "ask Gemini", "analyze with Gemini", "large file", "sandbox", "brainstorm with Gemini". Do not use for general code edits that do not require Gemini; use for tasks that benefit from Gemini's context or a second model.