Codebase analysis using Codex CLI with 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.
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Use Codex CLI for codebase analysis with read-only sandbox.
codex exec "Analyze this project structure and architecture. Do not make any changes. Respond with analysis only." --sandbox read-only --ask-for-approval never 2>&1
Full project analysis:
codex exec "Analyze this project. Report on:
- Overall architecture
- Key dependencies
- Component relationships
- Potential issues
Do not make any changes. Respond with analysis only." --sandbox read-only --ask-for-approval never 2>&1
Flow mapping:
codex exec "Map the authentication flow in this codebase. Identify all components involved. Do not make any changes. Respond with analysis only." --sandbox read-only --ask-for-approval never 2>&1
Dependency analysis:
codex exec "Analyze dependencies in this project:
- Direct vs transitive
- Outdated packages
- Circular dependencies
- Bundle size impact
Do not make any changes. Respond with analysis only." --sandbox read-only --ask-for-approval never 2>&1
Technical debt:
codex exec "Identify technical debt in this codebase:
- Deprecated patterns
- Inconsistent conventions
- Missing documentation
- Complex dependency chains
Do not make any changes. Respond with analysis only." --sandbox read-only --ask-for-approval never 2>&1
--dangerously-bypass-approvals-and-sandbox or --sandbox danger-full-access - these disable safety features and are forbidden--sandbox read-only to prevent file modifications--ask-for-approval never for non-interactive executioncodex --help to verify correct flag usagedangerouslyDisableSandbox: true for Bash callsreferences/setup.md for troubleshooting