oh-my-gemini

Perform thorough code review and audit of implemented features. Compares implementation against the technical plan, checks for AI-specific risks, and provides actionable feedback. Activate for: review, audit, code quality assessment, security review.

Initialize Conductor workflow in a project. Bundles all necessary templates for product context, tech stack, workflow, and tracks. v1.0: Hooks handle phase enforcement - setup focuses on file creation.

Persistence mode instructions for autonomous task completion. Activated when the user includes "ralph", "persistent", or "don't give up" in their prompt. Provides structured guidance for working through tasks systematically.

Structured research methodology for finding documentation, investigating APIs, and synthesizing technical information. Guides systematic research with source verification and organized output. Activate for: research, documentation lookup, investigate, explore concepts.

Plan and design a detailed, phased technical implementation from a PRD. Creates actionable task lists with guardrails for resource efficiency, error handling, and type safety. Activate for: plan, design, technical planning, task breakdown.

Generate documentation for implemented features. The actual code is always the source of truth - document what was built, not what was planned. Creates code comments, README updates, and developer guides as appropriate.

Execute a technical plan task by task, following the phased structure. v1.0: Hooks handle verification automatically - no manual reminders needed. Use when a technical plan exists and it's time to write code.

Generate comprehensive Product Requirements Documents (PRDs) through structured clarifying questions. Use when starting a new feature and need to define requirements before technical planning. Enforces "docs-first" methodology - no code until PRD exists.

Apply a minimal, targeted fix to a specific bug or issue. Focused on speed and precision - locate the problem, make the smallest correct change, and verify. Not a planning workflow; use for small fixes, patches, and hotfixes.

Safely restructure code while preserving behavior. Follows a strict safety protocol: verify clean git state, ensure tests pass before and after, verify types throughout. Use when code needs reorganization, cleanup, or structural improvement.

Create new Conductor tracks with spec, plan, and metadata files. Bundles all templates needed for track creation. Use when starting a new feature track via /omg:track or when manually creating tracks.

Systematic debugging assistant that helps identify and fix bugs through structured analysis, hypothesis testing, and root cause identification. Use when facing errors, unexpected behavior, or mysterious bugs.

Generate intelligent, conventional commit messages based on staged changes. Analyzes diffs, categorizes changes, and creates meaningful commit messages. Use when ready to commit changes and want high-quality commit history.

Continue working on a task until completion with automatic retry, self-verification, and alternative approaches. Activates "ralph mode" - never give up until the goal is achieved or explicitly impossible. Use when tasks require tenacity and iteration.

Generate comprehensive tests for code including unit tests, integration tests, and edge case coverage. Analyzes code to identify testable units and generates tests matching the project's testing framework and conventions.