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.
What this skill does
# 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:** ```bash agy --sandbox --print "Map the authentication flow in this project. Identify all components involved. Do not make any changes. Respond with analysis only." --dangerously-skip-permissions ``` **Dependency analysis:** ```bash agy --sandbox --print "Analyze this project's dependencies: - Direct vs transitive - Outdated packages - Circular dependencies - Bundle size impact Do not make any changes. Respond with analysis only." --dangerously-skip-permissions ``` **Technical debt:** ```bash agy --sandbox --print "Identify technical debt in this project: - Deprecated patterns - Inconsistent conventions - Missing documentation - Complex dependency chains Do not make any changes. Respond with analysis only." --dangerously-skip-permissions ``` ## Iterative Analysis Use `--continue` (still inside `--sandbox`) for multi-turn investigation: ```bash agy --sandbox --print "Analyze this project. Do not make any changes. Respond with analysis only." --dangerously-skip-permissions agy --continue --sandbox --print "What patterns did you find in the auth module? Do not make any changes. Respond with analysis only." --dangerously-skip-permissions agy --continue --sandbox --print "Are there security concerns with that pattern? Do not make any changes. Respond with analysis only." --dangerously-skip-permissions ``` ## Notes - **Google Antigravity must not make any changes; provide analysis ONLY.** `--sandbox` blocks shell side-effects, but the prompt-level clause keeps it from editing files in the workspace. - `agy` respects `.gitignore` — it cannot read files matching gitignore patterns. - Can take 5–10 minutes for large codebases; bump `--print-timeout` to `10m` or more for big jobs: ```bash agy --sandbox --print-timeout 10m --print "..." --dangerously-skip-permissions ``` - Requires sandbox bypass on the Bash tool: `dangerouslyDisableSandbox: true` (because Google Antigravity writes session state under `~/.gemini/`, shared with the old gemini-cli). - Use sessions for iterative exploration. - See `references/setup.md` and `references/patterns.md` for more.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.