ticket-reviewlisted

Review Acme Corp cache-cluster scaling change tickets from the Change Gateway. Use ONLY when the user explicitly asks to review, risk-analyze, or SOP-validate a SPECIFIC scaling change ticket, identified by a ticket URL such as https://gateway.acme.example/tickets/{id}, a bare ticket ID accompanied by review/analysis intent, or pasted ticket JSON (fields like ticket_id, cluster, change_type, current, target — pasted ticket content always counts as a review request). Fetches the ticket and its 7-day peak metrics, validates against the cache-scaling SOP, and renders a structured Markdown review comment. Do NOT use this skill for - ticket status lookups (e.g. "what's the status of ticket X" - answer directly), requests to approve or reject a ticket (decline - this DE never makes approval decisions), listing or searching tickets, or general questions about what the SOP says (answer those from the knowledge base without reviewing any ticket). Comment-only output; the decision stays with a human.
arthaszyb/bright-talent · ★ 0 · Code & Development · score 73

Install: claude install-skill arthaszyb/bright-talent

# Ticket Review (Cache-Cluster Scaling) Review cache-cluster scaling change tickets raised in the **Change Gateway** (mocked for this demo). Fetch the ticket and its 7-day peak metrics, apply the cache-scaling SOP, and post a structured pass/warn/fail review comment. **This skill never approves or rejects a ticket.** It produces a comment for a human reviewer to act on. ## When to trigger Trigger on: - A Change Gateway ticket URL, e.g. `https://gateway.acme.example/tickets/1002` - A bare ticket ID with review intent, e.g. "review this scaling ticket 1002" - Pasted ticket JSON/content with a request to review it Do **not** trigger (or trigger as review) on: - Pure status queries ("what's the status of ticket 1001") — that's a lookup, not a review; a review re-runs the SOP checks and produces a fresh comment - Any request to approve, reject, or otherwise act on the ticket ("approve ticket 1001") — this skill has no approve/reject capability by design; redirect the user to the Change Gateway's own approval action ## Inputs - **Ticket ID** (required): extracted from a Change Gateway URL (`https://gateway.acme.example/tickets/{id}`), a bare ID, or pasted content. - **Base URL** (optional): defaults to `http://localhost:8801`, the bundled mock server. Override only if the user names a different mock endpoint. ## Script pipeline All deterministic work — fetch, parse, compute, render — is scripted. The LLM's job is to orchestrate these four steps and present the res