Api Status Communication

samber/developer-platform-skills/skills/api-status-communication

作者 samber594cf70d343eMIT3 个星标收录于 2026年10月8日更新于 2026年10月8日仓库10天前更新

Design how an API platform communicates status and incidents to external consumers - status-page modeling (the four-stage incident lifecycle, degraded/partial/major component semantics, component granularity), monitoring-driven status instead of a hand-flipped green light, pull and push channels, incident-update cadence and templates, public postmortems for a developer audience, public SLA/SLO reporting, and maintenance-window notices. Use whenever the user mentions a status page, Statuspage, incident updates, uptime or SLA reporting, postmortems, or scheduled maintenance - even if they never say "status communication". Do NOT use for deprecation and breaking-change notices - use samber/developer-platform-skills@api-versioning-policy instead.

  1. 594cf70d343e当前提交 594cf70发布于 2026年10月8日

来源与署名

来源:samber/developer-platform-skills位于skills/api-status-communication提交594cf70

许可证: MIT

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架