Agent Skills
› kinncj/Heimdall
› sre-review
sre-review
GitHub评估新功能上线前的运维就绪状态，涵盖故障模式分析、可观测性指标与日志规范、告警策略及回滚计划。确保具备快速检测、恢复能力，并配套标准化运行手册以保障生产稳定性。
Trigger Scenarios
新功能发布前评审
生产环境变更准备
Install
npx skills add kinncj/Heimdall --skill sre-review -g -y
SKILL.md
Frontmatter
{
"name": "sre-review",
"description": "Evaluate operational readiness: SLOs, alerting, runbooks, and rollback plan before launch. Use when reviewing a feature for production readiness."
}
SKILL: SRE Review
Purpose
Evaluate operational readiness of new features before launch.
Failure Mode Analysis
For each new component, document:
- What can fail? (service down, latency spike, data corruption, cascade)
- Blast radius? (who is affected? how many users?)
- Detection time? (how quickly will alerts fire?)
- Recovery time? (how long to restore service?)
- Can it be rolled back? (feature flag? migration rollback?)
Observability Requirements
Metrics (Prometheus/CloudWatch/Datadog)
{feature}_requests_total{status="success|error"} counter
{feature}_request_duration_seconds histogram
{feature}_active_connections gauge
{feature}_errors_total{type="validation|timeout|upstream"} counter
Logs (Structured JSON)
{
"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}"
}
Traces
- Instrument all cross-service calls with OpenTelemetry.
- Trace IDs propagated via W3C Trace Context headers.
Alerts
| 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 |
Runbook Template
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}
Option B: Feature flag off
# Disable via environment variable
kubectl set env deployment/{service} FEATURE_{NAME}_ENABLED=false
Escalation
- On-call: {PagerDuty rotation}
- Escalation: {eng manager}
- War room: {Slack channel}
Version History
- f4ea31f Current 2026-07-05 10:42
