gemini-cli

Analyze large codebases beyond context limits to identify architecture and hotspots.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/seungwonme/.claude --skill gemini-cli-seungwonme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gemini-cli
Source: https://github.com/seungwonme/.claude/tree/main/achives/skills/gemini-cli
Command: npx skills add https://github.com/seungwonme/.claude --skill gemini-cli-seungwonme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze large codebases when context limits hinder deep insight, helping teams understand architecture and hotspots.

Core Features & Use Cases

  • Project-wide analysis across large repositories to reveal architecture, hotspots, and dependencies.
  • Cross-file and directory comparisons to detect consistency, patterns, and anti-patterns.
  • Verification of implementation across files exceeding 100KB or spanning multiple modules.

Quick Start

Use gemini -p with @ syntax to include files and directories for comprehensive analysis.

Frequently Asked Questions about gemini-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a large codebase when context limits prevent deep architectural insight?

To analyze a large codebase beyond context limits, you can include files and directories selectively using the @ syntax. This approach enables project-wide analysis to reveal architecture, dependencies, and hotspots.

What is the best way to perform cross-file comparisons to detect anti-patterns across multiple modules?

Cross-file and directory comparisons detect consistency, patterns, and anti-patterns across multiple modules. This method verifies implementation consistency across files exceeding 100KB or spanning multiple directories.

Can I use directory-wide reviews to verify implementation consistency in large repositories?

Directory-wide reviews verify implementation consistency across large repositories by supporting selective file inclusion. This allows you to compare files, detect architectural patterns, and ensure cross-file reasoning.

Does project-wide analysis work for files exceeding 100KB or spanning multiple modules?

Project-wide analysis supports verification of implementation across files exceeding 100KB or spanning multiple modules. It handles scalable project-wide analysis by allowing selective file inclusion and cross-file reasoning.

How do I identify architecture and hotspots across a full repository?

Identifying architecture and hotspots across a full repository requires comprehensive analysis using the @ syntax to include files and directories. This reveals dependencies and architectural patterns effectively.