Use this skill when the user wants a Gemini CLI companion workflow with explicit stages and boundaries.
Best fit
Use gemini-companion when the user wants Gemini to:
- review or analyze before implementation
- act as a structured second-pass companion rather than an ad-hoc command
- continue a previous Gemini-guided effort with explicit scope
- separate planning/review work from execution work
- stay within a clear Gemini-native workflow instead of generic shell usage
Positioning
| Skill | Best for |
|---|---|
gemini-companion |
Structured Gemini CLI companion workflow |
codex-companion |
Codex runtime lifecycle and persistent Codex task handling |
claude-code-companion |
Claude Code-native staged workflow |
| direct Gemini CLI usage | short one-off Gemini commands |
Working model
Treat this skill as a workflow layer around Gemini CLI.
Do not promise hidden persistent threads, job ids, or provider-native runtime lifecycle features unless they are actually available in the concrete Gemini environment being used.
Suggested flow
- Clarify the target and success criteria.
- Decide whether Gemini should:
- review first,
- provide a second opinion,
- help stage follow-up work,
- or execute a bounded focused task.
- Keep the workflow explicit.
- Verify any claimed outcome against files, diffs, or test results.
Guardrails
- Do not overpromise Codex-style lifecycle controls.
- Prefer precise workflow framing over “background magic”.
- If the user needs provider-specific persistent runtime semantics, state the limitation clearly.
- If the task is actually about Codex lifecycle commands, redirect to
codex-companion.