Document spike alerts feature

[mintlify]

Updated the billing alerts documentation to reflect the new spike alerts feature added in PR #2829. The documentation now explains both standard alerts (75%, 90%, 100%, 200%, 500%) and spike alerts (10x, 20x, 50x, 100x) that help catch runaway usage from bugs or errors.

Files changed

• docs/how-to-reduce-your-spend.mdx - Added section explaining the two types of billing alerts

Generated from Chore(webapp): Adds additional billing alerts @samejr

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2d1a40a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

PR Review: Document spike alerts feature

Summary

This is a documentation-only PR that adds 5 lines explaining the new spike alerts feature to the billing alerts section. The changes are well-scoped and directly support the feature added in PR #2829.

Review

✅ Code Quality & Best Practices

• The documentation follows the existing style and formatting conventions of the file
• Uses proper MDX syntax with bold formatting for alert type names
• The bullet point structure is consistent with other sections in the document
• Clear and concise explanations with helpful percentages for each threshold

✅ Content Accuracy

• Standard alerts (75%, 90%, 100%, 200%, 500%) and spike alerts (10x-100x) are clearly differentiated
• The percentage equivalents (e.g., "10x (1000%)") are helpful for users to understand the scale
• The recommendation to keep spike alerts enabled as a safety net is good guidance

✅ No Issues Found

• No security concerns (documentation only)
• No performance considerations (static content)
• No bugs or logic issues
• The referenced image billing-alerts-ui.png already exists in the repository

📝 Minor Suggestions (optional, non-blocking)

1. Consider whether the image billing-alerts-ui.png shows both types of alerts. If the UI was updated with the spike alerts feature, the screenshot may need updating to reflect the new options.
2. The phrase "We recommend keeping these enabled" could be made slightly more actionable, e.g., "We recommend keeping these enabled to protect against unexpected cost spikes." But this is a very minor point.

Verdict

LGTM ✅ - This is a clean, well-written documentation update that accurately describes the new spike alerts feature. Ready to merge.

[vibe-kanban-cloud]

Review Complete

Your review story is ready!

View Story

Comment !reviewfast on this PR to re-generate the story.