OpenSkillIndex← back to search
claude-codeautomation

Claude-skill-registry gemini-claude-loop

Dual-AI engineering loop orchestrating Claude Code (planning/implementation) and Gemini (validation/review). Use when (1) complex feature development requiring validation, (2) high-quality code with security/performance concerns, (3) large-scale refactoring, (4) user requests gemini-claude loop or dual-AI review. Do NOT use for simple one-off fixes or prototypes.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/gemini-claude-loop" ~/.claude/skills/majiayu000-claude-skill-registry-gemini-claude-loop && rm -rf "$T"
manifest: skills/data/gemini-claude-loop/SKILL.md
tags
#ai-assisted-coding#code-review#gemini#claude#dual-ai#code-generation
source content

Gemini-Claude Engineering Loop

Workflow Overview

Plan (Claude) → Validate (Gemini) → Implement (Claude) → Review (Gemini) → Fix → Re-validate → Done
RoleResponsibility
ClaudeArchitecture, planning, code implementation (Edit/Write/Read)
GeminiValidation, code review, quality assurance

Environment Notice

Non-TTY environment: See gemini-cli SKILL for CLI fundamentals. Key rule: Always use 

gemini -p "prompt"
(headless mode required)

Phase 0: Pre-flight Check

  1. Create context directory: 
    mkdir -p .gemini-loop
  2. Ask user via 
    AskUserQuestion
    :
    • Model preference (gemini-3-flash-preview (default), gemini-3-pro-preview (complex only))
    • Role mode preference (Review-Only OR Review+Suggest)

Phase 1: Planning (Claude)

  1. Create detailed implementation plan
  2. Break down into clear steps
  3. Document assumptions and risks
  4. Save to 
    .gemini-loop/plan.md

Phase 2: Plan Validation (Gemini)

Ask user for role mode, then execute with 

timeout: 600000
:

gemini -m gemini-3-flash-preview -p "Review this plan: $(cat .gemini-loop/plan.md) ..."

Full prompts by role mode: See commands.md

Save result: 

> .gemini-loop/phase2_validation.md

Phase 3: Feedback Loop

If issues found:

  1. Summarize Gemini feedback to user
  2. Ask via 
    AskUserQuestion
    : "Revise and re-validate, or proceed?"
  3. If revise → Update plan → Repeat Phase 2

Phase 4: Implementation (Claude)

  1. Implement using Edit/Write/Read tools
  2. Execute step-by-step with error handling
  3. Save summary to 
    .gemini-loop/implementation.md

Phase 5: Code Review (Gemini)

Execute with 

timeout: 600000
:

gemini -m gemini-3-flash-preview --include-directories ./src -p "Review: $(cat .gemini-loop/plan.md) $(cat .gemini-loop/implementation.md) ..."

Full prompts by role mode: See commands.md

Save result: 

> .gemini-loop/phase5_review.md

Claude response by severity:

  • Critical → Fix immediately
  • Architectural → Discuss with user
  • Minor → Document and proceed

Phase 6: Iteration

  1. Apply fixes from 
    .gemini-loop/phase5_review.md
  2. Significant changes → Re-validate with Gemini
  3. Loop until quality standards met

Context Files

.gemini-loop/
├── plan.md               # Implementation plan
├── phase2_validation.md  # Plan validation result
├── implementation.md     # Implementation summary
├── phase5_review.md      # Code review result
└── iterations.md         # Iteration history

Quick Reference

Always use 

timeout: 600000
(10 min) for all Gemini commands.

References