Officialv1.0.03 scenarios
Prometheus Rules
Prometheus rule guidance for alert timing, recording rules, and query-cardinality safety.
deploywhisper skill install prometheus-rules
How to use this skill
1. Install it locally
Use the install command above from any DeployWhisper app checkout that has the installer enabled.
2. Run analysis on matching artifacts
This skill activates when files or content patterns below are detected during analysis.
3. Verify behavior
Published registry data currently includes 3 deterministic scenarios for this skill.
Metadata
Author
DeployWhisper
Version
1.0.0
License
MIT
Scenarios
3
Tags
Triggers
- prometheus-rules.yaml
- alerting-rules.yaml
Content patterns
- kind: PrometheusRule
Guidance excerpt
Critical risk patterns
- Extending alert `for:` windows delays paging and can hide fast-burning incidents = HIGH
- Recording rule renames break downstream dashboards, alerts, and SLO calculations = MEDIUM
- Unbounded joins or label expansions can overload Prometheus and remote-write pipelines = HIGH
- Severity label downgrades reduce response urgency even when the underlying blast radius is unchanged = HIGH
Review cues
- Review Prometheus rule semantics, cardinality impact, and downstream consumers before merging.
- Prefer deterministic roll-forward or rollback steps over hand-wavy remediation notes.