Language: 日本語English

rootly Plugin

Author
Rootly
Category
Monitoring
Topics
Monitoring & Observability · Cloud, Deployment & CI/CD · Claude Code Customization & Workflow
First seen
2026-07-09
Last confirmed
2026-07-13
Explanation last updated
2026-07-12

The explanation below is AI-generated. Please verify it against the sources.

Rootly for Claude Code is a Claude Code plugin (Apache 2.0, hosted on GitHub) that brings Rootly's incident lifecycle into the terminal. According to the README, it covers deploy-risk checks, incident response, on-call management, and retrospectives through slash commands and specialized agents. Stable commands connect via the Rootly MCP server using OAuth2, while a small set of experimental commands delegate to forked subagents that may lose MCP access in some contexts. Hook scripts that warn about active incidents on commit/push use a separate API token. According to the homepage, Rootly itself is described as an AI-native incident management platform with On-Call, Incident Response, AI SRE, Retrospectives, and Status Page products.

Overview

According to the homepage, Rootly is described as an "AI-native incident management platform" offering On-Call, Incident Response, AI SRE, Retrospectives, and Status Page products, and it is positioned as an alternative for teams switching from PagerDuty.

What you can do with rootly

  • Run /rootly:deploy-check to analyze a git diff against past incidents and check on-call coverage before deploying
  • Run /rootly:respond [id] to pull full incident context, similar past incidents, and suggested solutions
  • Run /rootly:oncall to view on-call schedules, shift metrics, and upcoming handoffs
  • Run /rootly:status [service] to see active incidents grouped by severity and age
  • Run /rootly:brief [id] to generate executive-friendly incident summaries
  • Run /rootly:handoff to create structured handoff documents for incident commanders or on-call transitions
  • Run /rootly:ask [question] for natural-language queries over incident and on-call data
  • Run /rootly:retro [id] to generate a structured retrospective (timeline, contributing factors, action items)
  • Use additional README-listed commands such as /rootly:my, /rootly:alert, /rootly:lookup, /rootly:trend, /rootly:action, /rootly:swap, /rootly:cover, and /rootly:announce
  • Rely on automatic hooks that check your API token at session start and warn about active critical incidents before git commit/git push

Sources

Original description (English)

Full-lifecycle incident management: deploy safety, incident response, on-call management, and retrospectives.

History of rootly

Back to list