claude-role-packslisted

# Claude Role Packs Use this skill when the user wants a named Claude reviewer team instead of spelling out each role. List built-in packs: ```bash node "${CODEX_PLUGIN_ROOT}/scripts/claude-companion.mjs" roles list ``` Inspect one pack: ```bash node "${CODEX_PLUGIN_ROOT}/scripts/claude-companion.mjs" roles inspect "$ARGUMENTS" ``` Validate a user-authored JSON pack: ```bash node "${CODEX_PLUGIN_ROOT}/scripts/claude-companion.mjs" roles validate "$ARGUMENTS" ``` Run a built-in pack: ```bash node "${CODEX_PLUGIN_ROOT}/scripts/claude-companion.mjs" multi-review --role-pack "$ARGUMENTS" ``` ## Natural-Language Claude Routing <!-- routing:role-packs routing:role-pack-executable-builtins-only --> - Do not ask the user to write `--quality`, `--model`, or `--effort` unless troubleshooting the plugin itself. - Keep Codex responsible for reconciling Claude output before edits. - Route named reviewer-team requests to built-in role packs when an existing pack matches the intent. - Keep user-authored role packs validate/inspect-only; do not execute them. - Do not substitute strong local Claude routing with `claude ultrareview`; ultrareview requires the claude-ultrareview skill and explicit cost confirmation. User-facing examples: - "List the Claude reviewer teams." - "Use the release reviewer team for this branch." - "Validate this custom reviewer pack." Internal routing procedure: - Classify the user's intent first, then invoke the narrowest Claude for Codex command that s