subagent

rootly-incident-responder — Claude Code subagent: install

Q: How do I install rootly-incident-responder in Claude Code?

Run `npx claude-code-templates@latest --agent development-tools/rootly-incident-responder`, then use `.claude/agents/rootly-incident-responder.md`.

A Claude Code subagent for Rootly incident triage, historical matches, on-call coordination, and reviewed remediation plans.

Install into Claude Code · claude-code-templates All methods and platforms ↓

npx claude-code-templates@latest --agent development-tools/rootly-incident-responder

Open on GitHub

What rootly-incident-responder does

rootly-incident-responder gathers incident details from Rootly, including severity, affected services, environment, status, and alert order. It searches earlier incidents for related cases and uses their outcomes to suggest possible responses.

The subagent can identify the current on-call team, account for regional coverage, and compare the incident with recent GitHub changes. Its reports include sources, confidence, and reasoning; production rollbacks and other high-impact actions stay behind a human approval step.

A Rootly MCP server is required for the incident workflow. GitHub MCP is optional and supports code-change correlation. Without Rootly MCP, the subagent cannot work with Rootly data.

What it helps with

investigate a production incident
match an outage with earlier Rootly incidents
compare a failure with recent GitHub changes
prepare a handoff for the on-call team
draft a remediation plan for approval

Example prompts for the agent

Investigate incident INC-123 in Rootly, find related incidents, and show confidence for each lead.
Identify the first alerts in this incident and compare the timeline with recent GitHub changes.
Draft remediation actions and wait for my approval before any critical production change.

How to install rootly-incident-responder

1claude-code-templates

npx claude-code-templates@latest --agent development-tools/rootly-incident-responder

2Manually: put the files in place

.claude/agents/rootly-incident-responder.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Manually: put the files in place

.codex/agents/rootly-incident-responder.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Manually: put the files in place

.cursor/agents/rootly-incident-responder.md

Cursor also reads .claude/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about rootly-incident-responder

How do I install rootly-incident-responder in Claude Code?

Run npx claude-code-templates@latest --agent development-tools/rootly-incident-responder, then use .claude/agents/rootly-incident-responder.md.

What does rootly-incident-responder do?

It examines Rootly incidents, finds related historical cases, suggests response options, identifies on-call context, and prepares remediation plans.

What does the subagent need to work?

It requires a Rootly MCP server. GitHub MCP is optional and is used to connect incidents with code changes.

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

frontend-developer VoltAgent Community Subagent for building complete frontend applications with React 18+, Vue 3+, and Angular 15+. Handles component architecture, state management, testing, and accessibility. 40,905installs dx-optimizer VoltAgent Community Subagent profiles and accelerates your entire development cycle: build times, feedback loops, testing. Use it when the project is slow or developers waste time waiting. 1,198installs mlops-engineer VoltAgent Community This subagent designs ML infrastructure, model CI/CD, and versioning workflows. Use it when training automation, GPU orchestration, or ML monitoring needs attention. 1,009installs postgres-pro VoltAgent Community A PostgreSQL subagent for query tuning, replication design, backups, and database troubleshooting. Use it when performance or high-availability work needs a structured review. 897installs agent-installer VoltAgent Community Subagent for discovering, browsing, and installing Claude Code agents from the awesome-claude-code-subagents repository. Simplifies finding and integrating new tools into your workflow. 363installs embedded-systems VoltAgent Community A subagent for microcontroller firmware work with memory, power, and real-time constraints in mind. Use it for RTOS tasks, drivers, and peripheral integration. 279installs

From the same set740

The whole set →

arm-migration A subagent that hunts x86 assumptions in your repo and helps move builds and container images to ARM64. Made for teams heading to Arm infrastructure. 169installs powershell-windows Defines patterns for Windows PowerShell scripts, enforcing cmdlet parentheses, pure ASCII console output, and safe JSON parsing. Solves common syntax crashes. 169installs geo-fundamentals Use this skill to assess whether site content is ready to appear in AI-generated answers. It covers content structure, crawler access and citation tracking. 168installs team-workload-balancer Analyzes developer workload, matches skills to sprint tasks, and balances assignments using local Git logs and Linear. 167installs voidbeast-gpt41enhanced An autonomous full-stack subagent that picks its own mode, digs through the codebase and keeps working until the problem is solved. 166installs javascript-mastery JavaScript reference skill for Claude Code covering core language mechanics, closures, event loop queues, and tricky runtime behavior. 165installs console-log-cleaner This hook looks for console. lines when editing JavaScript and TypeScript files on production branches. It can flag debug output before changes are merged. 165installs screenshot-analyzer Runs parallel subagents on interface screenshots to extract UI components, flows, and business rules into a Markdown task list. 165installs