review-agentic-setup

# Review Agentic Setup Detect agentic coding infrastructure and flag gaps across Claude Code and Codex CLI conventions. Analysis only. Does not install or configure anything. ## Scope Agentic setup review always operates at the project level. Scope parameters (diff commands, file lists) are accepted but ignored. When called standalone, use the git repository root as the project root (fall back to the current working directory if not in a git repo). ## Step 1: Detect Infrastructure Search for agentic coding configuration in the project. Classify findings into five categories: ### Agent Instructions | File | Read by | What to check | |---|---|---| | `CLAUDE.md` (project root) | Claude Code | Exists? Sections present (project structure, conventions, build commands, rules)? | | `CLAUDE.md` (subdirectories) | Claude Code | Any nested CLAUDE.md files for sub-module guidance? | | `AGENTS.md` (root and subdirectories) | Codex | Exists? Content areas (setup, conventions, testing, architecture)? | | `AGENTS.override.md` | Codex | Exists? Overrides AGENTS.md at the same directory level. | | `README.md` | Both | Mentions AI-assisted development, agent workflows, or prompting guidance? | Read each file that exists and summarize its coverage areas. Note which tools can use it. Claude Code does not read AGENTS.md directly. Projects share instructions across both tools by: - **Import**: CLAUDE.md includes `@AGENTS.md` to pull in shared content - **Symlink**: `CLAUDE.md` symlinked ...