Use when the user wants the Claude `/deploy` command workflow in Codex, or asks to run `deploy` using the claudet command template.
Use when the user wants the Claude `/fix-issue` command workflow in Codex, or asks to run `fix-issue` using the claudet command template.
Use when the user wants the Claude `/review` command workflow in Codex, or asks to run `review` using the claudet command template.
Use when syncing, auditing, or converting Claude Code and Codex project configuration; when the user says "sync agent configs", "convert Claude project to Codex", "convert Codex project to Claude", "make this project work with both Claude and Codex", or asks to keep AGENTS.md, CLAUDE.md, .claude, .codex, .mcp.json, agents, commands, and skills aligned.
Use when starting a new project from scratch and wanting Claude Code or Codex conventions; when the user says "scaffold from the template", "use claudet", "set up a new project", "init claude config in this repo", "init codex config in this repo", or asks to copy rules/agents/commands/claudedocs structure from the claudet template repo.
Use when the user wants to install or update the claudet rule library (`code-style`, `naming-and-comments`, `file-and-module-structure`, `dependency-management`, `testing`, `api-conventions`, `documentation`) into the current project's `.claude/rules/`; when the user says "sync rules from claudet", "install standard rules here", "update rules in this project", or asks why their rules look outdated compared to claudet's.
Use when designing or reviewing CI/CD pipelines or GitHub Actions workflows; when auditing CI for security or quality gaps; when picking tools (gitleaks, semgrep, trivy, osv-scanner, etc.); when deciding what should fail-the-build vs warn; when shipping AI-generated code that needs harder gates than human code; when a PR slipped through with secrets, hallucinated APIs, broken migrations, or uncovered branches.
Use when about to dispatch a long-running agent task that will modify files and the user wants to keep editing the main checkout; when planning to run two or more agents in parallel on the same repo and worried about file-edit collisions; when reviewing a PR or running a risky/experimental edit without losing current uncommitted state; when bisecting a bug across branches; when comparing two implementations side-by-side; when a destructive operation (large refactor, dependency upgrade, codemod) needs an escape hatch.