Codebase Analysis
Deep architectural analysis of the current workspace using Google Antigravity (`agy`). Trigger when the user needs an architecture overview ("analyze this codebase with agy", "map dependencies with Google Antigravity"), is onboarding to unfamiliar code, exploring legacy systems, or hunting technical debt. Replaces the deprecated gemini-cli `codebase_investigator` workflow.
Install
/plugin marketplace add robbyt/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add robbyt/claude-skills --skill codebase-analysisgit clone --depth 1 https://github.com/robbyt/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/agy/skills/codebase-analysis ~/.claude/skills/codebase-analysisPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Codebase Analysis via Google Antigravity (`agy`) Use Google's Antigravity CLI for deep architectural analysis. `agy` is Google's agentic successor to `gemini-cli` and runs Google's Gemini models — it can roam the workspace, follow references, and surface structure that surface-level grep cannot. ## Why `--sandbox` Here Codebase analysis benefits from broad workspace access — `agy` needs to read many files, follow imports, and chase references. But it should not run arbitrary shell commands while doing so. Google Antigravity has no `--allowed-tools` flag, so use `--sandbox` to grant file access while denying shell execution: ```bash agy --sandbox --print "..." --dangerously-skip-permissions ``` Pair `--sandbox` with a "Do not make any changes" clause for belt-and-suspenders safety. ## Quick Start ```bash agy --sandbox --print "Analyze this project's architecture. Do not make any changes. Respond with analysis only." --dangerously-skip-permissions ``` ## When to Use - Onboarding to unfamiliar codebases - Understanding legacy systems - Mapping component relationships - Finding hidden dependencies - Architecture documentation - Technical debt assessment ## Examples **Full project analysis:** ```bash agy --sandbox --print "Analyze this project. Report on: - Overall architecture - Key dependencies - Component relationships - Potential issues Do not make any changes. Respond with analysis only." --dangerously-skip-permissions ``` **Flow mapping:**
Details
- Skill name
codebase-analysis- Repository
- robbyt/claude-skills
- Path
plugins/agy/skills/codebase-analysis/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Codebase Analysis skill do?
Deep architectural analysis of the current workspace using Google Antigravity (`agy`). Trigger when the user needs an architecture overview ("analyze this codebase with agy", "map dependencies with Google Antigravity"), is onboarding to unfamiliar code, exploring legacy systems, or hunting technical debt. Replaces the deprecated gemini-cli `codebase_investigator` workflow.
How do I install the Codebase Analysis skill?
Claude Code plugin: /plugin marketplace add robbyt/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Codebase Analysis popular?
It lives in robbyt/claude-skills, which has 42 GitHub stars and 2 forks.
Related skills
Actions
42robbyt/claude-skills
GitHub Actions workflow management using GitHub CLI. Trigger when user wants to check CI status ("check CI", "is the build passing"), view workflow runs ("show recent runs", "view action logs"), watch running workflows ("watch CI"), or rerun failed workflows ("rerun the build").
Adversarial Review
42robbyt/claude-skills
Have Codex try to break a change before it ships — a skeptical review that challenges the design, assumptions, and failure modes of a diff or branch and returns structured findings (verdict, severity, file:line, confidence). Trigger on "adversarial review", "challenge this change/design with Codex", "pressure-test this before I ship", "have Codex try to break this", "is this safe to merge", or a review focused on a risk area (auth, data loss, rollback, race conditions, retries). Do NOT use for a routine bug/style pass over a diff (that's diff-review), for critiquing a plan before code exists (
API Review
42robbyt/claude-skills
This skill should be used when reviewing API designs, auditing REST or gRPC endpoints, designing backend APIs, evaluating BFF architecture, or discussing API best practices. Also triggers on: "review this API", "API design review", "is this API correct", "REST API audit", "gRPC API review", "PATCH vs PUT", "etag", "idempotency", "pagination design", "API error handling", "backward compatibility", "BFF architecture", "resource-oriented design", "TOCTOU", "race condition", "optimistic concurrency", "field mask", "long-running operation", "custom method", "soft delete", "API naming conventions",
Codebase Analysis
42robbyt/claude-skills
Codebase analysis via the Codex MCP server with a read-only sandbox. Trigger when user needs architecture overview ("analyze this codebase with Codex", "have Codex map dependencies"), onboarding to unfamiliar code, understanding legacy systems, or identifying technical debt.
Codebase Analysis
42robbyt/claude-skills
Deep architectural analysis using Gemini's codebase_investigator tool. Trigger when user needs architecture overview ("analyze this codebase", "map dependencies"), onboarding to unfamiliar code, understanding legacy systems, or identifying technical debt.
Go Style Guide
42robbyt/claude-skills
Review Go code for adherence to Go Style Guide. Use when the user requests a code review of completed work, pull requests, or feature branches in Go projects. Focuses on critical bugs, race conditions, and important maintainability issues. Trigger phrases include "review this Go code", "check against style guide", "review my PR", or "review the work done so far".
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.