feat: add zeabur-service-metric skill for performance diagnostics#36
feat: add zeabur-service-metric skill for performance diagnostics#36eliajhmauve wants to merge 1 commit intozeabur:mainfrom
Conversation
Adds a skill covering `service metric CPU/MEMORY/NETWORK` with a diagnostic workflow that teaches the AI to check metrics BEFORE blindly restarting. Includes a decision table mapping symptoms to likely causes and recommended actions. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
Summary
zeabur-service-metricskill coveringservice metric CPU/MEMORY/NETWORKWhy this skill?
When users report "my service is slow", the AI currently has no way to check resource usage — it just suggests restarting. This skill gives the AI a proper diagnostic path: check metrics → identify bottleneck → take appropriate action.
Test plan
service metric CPU/MEMORY/NETWORK --id <id> -i=falsereturns data on a live service--hourflag for custom time windowszeabur-restartfor reference)🤖 Generated with Claude Code