\n\n| \n\n### Before You Deploy\n```\n> /rootly:deploy-check\n```\nAnalyzes your git diff against past incidents. Warns you if similar changes caused outages before. Checks if on-call coverage exists.\n\n | \n\n\n### When You Get Paged\n```\n> /rootly:respond INC-4521\n```\nPulls full incident context, finds similar past incidents, suggests proven solutions, and shows who's on-call -- all in one brief.\n\n | \n
\n\n| \n\n### During Your Shift\n```\n> /rootly:oncall\n```\nSee who's on-call across all schedules, shift metrics, upcoming handoffs, and health risk indicators.\n\n | \n\n\n### Service Health Check\n```\n> /rootly:status\n```\nQuick overview of all services with active incidents grouped by severity and age.\n\n | \n
\n\n| \n\n### Stakeholder Communication\n```\n> /rootly:brief INC-4521\n```\nGenerate executive-friendly incident summaries with impact, timeline, and current status for stakeholder updates.\n\n | \n\n\n### Shift Handoffs\n```\n> /rootly:handoff\n```\nCreate structured handoff documents for incident commanders or on-call transitions with context and next steps.\n\n | \n
\n\n| \n\n### Ask Questions\n```\n> /rootly:ask \"incidents this week\"\n```\nNatural language queries about your incident data, on-call schedules, and service reliability patterns.\n\n | \n\n\n### After the Dust Settles\n```\n> /rootly:retro INC-4521\n```\nGenerates structured retrospectives from incident data: timeline, contributing factors, action items, and systemic patterns.\n\n | \n
\n
\n\n## Installation\n\nYou can use this plugin in two ways:\n\n- **Marketplace install** for a persistent Claude Code installation\n- **Local `--plugin-dir` loading** for development and evaluation from source\n\n### Marketplace Install\n\nThis repository includes `.claude-plugin/marketplace.json`, so Claude Code can use the repo itself as a marketplace source.\n\n1. Add the marketplace:\n\n```text\n/plugin marketplace add Rootly-AI-Labs/rootly-claude-plugin\n```\n\n2. Open the plugin manager:\n\n```text\n/plugin\n```\n\n3. In the **Discover** tab, select `rootly` and install it to your preferred scope:\n\n- **User**: available across all your projects\n- **Project**: shared through this repository's `.claude/settings.json`\n- **Local**: only for you in this repository\n\n4. Reload plugins so the install takes effect immediately:\n\n```text\n/reload-plugins\n```\n\n5. Run setup -- Claude will automatically handle OAuth2 login when it connects to the MCP server:\n\n```text\n/rootly:setup\n```\n\nA browser window will open for you to log in to Rootly and grant access. No API token needed.\n\n### Local Source Loading\n\n#### Step 1: Clone the Plugin\n\n```bash\ngit clone https://github.com/Rootly-AI-Labs/rootly-claude-plugin.git\ncd rootly-claude-plugin\n```\n\n#### Step 2: Load It in Claude Code\n\n```bash\nclaude --plugin-dir .\n```\n\nClaude Code loads the plugin directly from this directory for the current session. This is the recommended flow for local development and evaluation. For a persistent install, use the marketplace flow above.\n\n#### Step 3: Verify\n\n```\n/rootly:setup\n```\n\n### Direct MCP Access\n\nThis repository is a Claude Code plugin. If you only want direct Rootly MCP access in Claude Desktop / Cowork, configure the MCP server separately:\n\n```json\n{\n \"mcpServers\": {\n \"rootly\": {\n \"url\": \"https://mcp.rootly.com/mcp\"\n }\n }\n}\n```\n\nClaude will handle OAuth2 login automatically -- a browser window opens for you to authenticate with Rootly. No API token needed.\n\n---\n\n## Setup & Configuration\n\nAfter installation, run the setup command:\n```\n> /rootly:setup\n```\nFirst-time plugin setup with API token validation, service mapping, and quick-start guide.\n\n---\n\n## Authentication\n\n### OAuth2 (Recommended)\n\nMCP commands use OAuth2 automatically. When Claude connects to the Rootly MCP server, it handles the OAuth2 flow -- a browser window opens for you to log in and grant access. No configuration needed.\n\nTo re-authenticate, disconnect and reconnect the MCP server via `/mcp`.\n\n### API Token (Hook Scripts)\n\nHook scripts (active-incident warnings on commit/push) still use API tokens since they run outside the MCP context:\n\n```bash\n# Via plugin config (persistent)\n# Set ROOTLY_API_TOKEN in the plugin's userConfig prompt\n\n# Via env var (session-scoped)\nexport ROOTLY_API_TOKEN=\"your-token-here\"\n```\n\nGet a token from your Rootly dashboard under **Settings > API Keys**.\n\n---\n\n## Commands\n\n### Stable (inline, MCP-native)\n\n| Command | What It Does |\n|---------|-------------|\n| `/rootly:setup` | First-run configuration and connection check |\n| `/rootly:my` | Personal dashboard — your active incidents, action items, and upcoming on-call |\n| `/rootly:status [service]` | Service health overview — active incidents at a glance |\n| `/rootly:oncall [team]` | On-call dashboard with shift metrics |\n| `/rootly:alert [short-id]` | Triage a Rootly alert — events, group context, linked incident |\n| `/rootly:lookup [name]` | Look up a service, team, or catalog entity — owner, on-call, reliability |\n| `/rootly:trend [scope]` | 30-day reliability trend with prior-period comparison |\n| `/rootly:brief [id]` | Stakeholder summary for executives or customers |\n| `/rootly:handoff [id]` | Incident or on-call handoff documentation |\n| `/rootly:ask [question]` | Natural-language Q&A over your Rootly data |\n| `/rootly:action [list\\|add\\|done]` | Manage incident action items (write actions confirm before mutating) |\n| `/rootly:swap [date]` | Request someone cover one of your shifts (write, confirms first) |\n| `/rootly:cover [team]` | Offer to cover someone else's shift (write, confirms first) |\n| `/rootly:announce [id]` | Draft and post a stakeholder update on an incident (write, confirms first) |\n\n### Experimental (forked subagent — may not have MCP access in all contexts)\n\n| Command | What It Does |\n|---------|-------------|\n| `/rootly:respond [id]` | Deep incident investigation via the `incident-investigator` agent |\n| `/rootly:retro [id]` | Post-incident retrospective via the `retro-analyst` agent |\n| `/rootly:deploy-check` | Pre-deploy risk analysis via the `deploy-guardian` agent |\n\n> The experimental skills delegate to forked subagents. In some Claude Code contexts the subagent doesn't inherit the plugin's MCP server; when that happens it stops and reports rather than falling back to bash/curl (which would leak the API token). For reliable coverage of those workflows, prefer `/rootly:brief`, `/rootly:status`, and the inline alternatives above.\n\n### Natural Language Queries\n\n```\n/rootly:ask how many SEV-1 incidents did we have last month?\n/rootly:ask which service has the most incidents this quarter?\n/rootly:ask who's been on-call the most in the last 30 days?\n```\n\n---\n\n## Deep Investigation Agents\n\nWhen a slash command isn't enough, Claude automatically invokes specialized agents for deeper analysis:\n\n| Agent | Triggered When | What It Does |\n|-------|---------------|--------------|\n| **Incident Investigator** | You need root cause analysis beyond initial triage | Builds hypothesis trees, correlates alerts with code changes, traces causation chains |\n| **Deploy Guardian** | Multi-service deployments with cross-team impact | Maps blast radius across dependent services, evaluates downstream risk, builds coordination checklists |\n| **Retro Analyst** | You want to understand patterns across incidents | Clusters incidents by failure mode, calculates frequency trends, identifies systemic reliability issues |\n\n---\n\n## Automatic Hooks\n\nTwo lightweight hooks run in the background -- they **never block** your workflow:\n\n| Hook | When | What It Does |\n|------|------|--------------|\n| **Token check** | Session start | Validates your API token and nudges you to configure one if missing |\n| **Incident warning** | Before `git commit` / `git push` | Warns if there's an active critical incident -- so you don't deploy into a fire |\n\n---\n\n## Service Mapping\n\nMap your repository to Rootly services by creating `.claude/rootly-config.json`:\n\n```json\n{\n \"services\": [\"auth-service\", \"auth-worker\"],\n \"team\": \"platform-team\"\n}\n```\n\n`/rootly:setup` walks you through creating this. Without it, the plugin falls back to matching your git repo name against Rootly service names.\n\n---\n\n## Advanced\n\n![\"Rootly](\"assets/logo.png\"){kind=logo}
\n![\"Rootly](\"https://img.shields.io/badge/rootly-integration-D97757?style=flat-square&logo=data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMjQiIGhlaWdodD0iMjQiIHZpZXdCb3g9IjAgMCAyNCAyNCIgZmlsbD0ibm9uZSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj48Y2lyY2xlIGN4PSIxMiIgY3k9IjEyIiByPSIxMCIgZmlsbD0id2hpdGUiLz48L3N2Zz4=\"){kind=icon}
![\"License\"](\"https://img.shields.io/badge/license-Apache%202.0-blue?style=flat-square\"){kind=icon}
![\"Claude](\"https://img.shields.io/badge/claude--code-plugin-4A154B?style=flat-square\"){kind=icon}