メニュー
Evaluate operational readiness: SLOs, alerting, runbooks, and rollback plan before launch. Use when reviewing a feature for production readiness.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | sre-review |
| description | Evaluate operational readiness: SLOs, alerting, runbooks, and rollback plan before launch. Use when reviewing a feature for production readiness. |
Evaluate operational readiness of new features before launch.
For each new component, document:
{feature}_requests_total{status="success|error"} counter
{feature}_request_duration_seconds histogram
{feature}_active_connections gauge
{feature}_errors_total{type="validation|timeout|upstream"} counter
{
"timestamp": "ISO8601",
"level": "info|warn|error",
"service": "{service-name}",
"trace_id": "{distributed-trace-id}",
"user_id": "{anonymized}",
"action": "{what happened}",
"duration_ms": 42,
"result": "success|error",
"error": "{message if error}"
}
| Alert | Condition | Severity | Action |
|---|---|---|---|
| High error rate | error_rate > 1% for 5m | P1 | Page on-call |
| Slow responses | p99 > 2s for 10m | P2 | Notify team |
| Saturation | CPU > 80% for 15m | P2 | Scale out |
docs/runbooks/{feature}-runbook.md
# Runbook: {Feature Name}
## Symptoms
- {Alert name}: {what the user sees}
## Diagnosis
1. Check logs: `kubectl logs -l app={service} --tail=100`
2. Check metrics: {dashboard URL}
3. Check dependencies: {health check commands}
## Mitigation
### Option A: Restart service
```bash
kubectl rollout restart deployment/{service}
kubectl rollout status deployment/{service}
# Disable via environment variable
kubectl set env deployment/{service} FEATURE_{NAME}_ENABLED=false
Manage GitHub Projects v2 board: add issues, update field values, and query board state. Use when managing project boards.
Run WCAG 2.2 Level AA accessibility audits against generated UI. Use when a story has ui:true or when asked to audit accessibility.
Generate a complete component file tree wired to design tokens with tests and Gherkin spec. Use when scaffolding a new UI component.
Extract Gherkin scenarios from story markdown files into runnable .feature files and generate step definition stubs. Use when syncing stories to test suites.
Read and write design tokens in W3C DTCG format (tokens.json) and emit CSS, Tailwind, and Mantine outputs. Use when modifying or generating design tokens.
Apply Docker and Docker Compose best practices for containerising services. Use when writing or reviewing Dockerfiles and compose configs.