Update to Zuora Coding Agent

{
  "description": "Review work for Zuora best practices",
  "included_files": [],
  "name": "zuora-review",
  "skill_md_contents": "---\nname: zuora-review\ndescription: Review work for Zuora best practices\nargument-hint: [file path or description of what to review]\nallowed-tools: [Read, Glob, Grep, Bash, Agent, mcp__zuora-mcp__zuora_codegen, mcp__zuora-mcp__ask_zuora, mcp__zuora-mcp__query_objects]\n---\n\nCodex-only path resolution: When an instruction refers to `${CLAUDE_PLUGIN_ROOT}`, treat it as the root of this installed plugin. In Codex, resolve that root as the ancestor directory containing `skills/`, `references/`, and `.codex-plugin/`.\n\n\nYou are reviewing Zuora-related implementation work for best practices, completeness, and correctness. This is broader than `/zuora-validate` — it evaluates the overall approach, not just individual code correctness.\n\n## Input\n\nWhat to review: $ARGUMENTS\n\n## Tool routing\n\nUse local file reads and bundled references for implementation facts and baseline best practices. Use `mcp__zuora-mcp__zuora_codegen` for SDK/API-specific rules and `mcp__zuora-mcp__query_objects` only when tenant state matters to the review. Use `mcp__zuora-mcp__ask_zuora` only for a concrete product-behavior or best-practice judgment that remains unresolved after those sources.\n\n## Workflow\n\n### Step 1: Understand scope\n\nRead the files or description. Determine what aspects to review:\n- API integration code\n- Workflow implementation\n- Migration plan or scripts\n- Product catalog setup\n- Template/form design\n- Overall architecture and approach\n\n### Step 2: Gather Zuora context\n\nUse MCP tools as needed:\n- `mcp__zuora-mcp__ask_zuora` — for unresolved product-level best-practice questions; prefer reading the bundled references (Step 3) first when they are likely to have the answer, but call earlier if the question is clearly qualitative\n- `mcp__zuora-mcp__zuora_codegen` with `code_rules` — for SDK-specific patterns\n- `mcp__zuora-mcp__query_objects` — to check tenant state if relevant to the review\n\n### Step 3: Read reference material\n\nRead the relevant files from `${CLAUDE_PLUGIN_ROOT}/references/`:\n- `best-practices.md` — always read for general Zuora best practices\n- `api-integration-patterns.md` — for API integration reviews\n- `workflow-patterns.md` — for workflow reviews\n- `is-migration-patterns.md` — for IS migration reviews\n- `order-migration-patterns.md` — for Order API migration reviews\n\n### Step 4: Evaluate across dimensions\n\n- **Correctness**: Do API calls use correct endpoints, fields, and enum values?\n- **Completeness**: Are all required steps present (auth, error handling, pagination, cleanup)?\n- **Robustness**: Error handling, retries, idempotency, rate limiting, STOP_AND_CONFIRM handling?\n- **Performance**: Efficient API usage, appropriate batching, avoiding N+1 query patterns?\n- **Security**: No hardcoded credentials, proper token management, secrets in environment variables?\n- **Maintainability**: Clean structure, appropriate abstractions, configuration externalized?\n- **Zuora-specific**: Following Zuora's recommended patterns for the specific use case?\n- **Testing**: Is there a strategy for testing (sandbox, mocks, integration tests)?\n\n### Step 5: Deliver the review\n\n**Summary**: Overall assessment in 1-2 sentences\n\n**Strengths**: What is done well (2-3 points)\n\n**Issues** (prioritized by severity):\nFor each issue:\n- Severity (critical / major / minor)\n- Description\n- Recommended fix\n\n**Suggestions**: Non-blocking improvements for consideration\n\n**Next steps**: What to do after addressing the review findings\n"
}