cveralyon

Incident — Development agent for Claude Code

Development community

Production incident response — gather logs, recent deploys, commits, Linear issues, draft summary.

How to install Incident

Installs to ~/.claude/agents/cveralyon-axel-setup-incident.md

Terminal
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/cveralyon/axel-setup/HEAD/agents/incident.md -o ~/.claude/agents/cveralyon-axel-setup-incident.md

Restart Claude Code, or start a new session, for it to be picked up.

What Incident does


description: Production incident response — gather logs, recent deploys, commits, Linear issues, draft summary. tools: ["Bash", "Read", "Grep", "Glob", "mcp__claude_ai_Linear__list_issues", "mcp__claude_ai_Linear__search_documentation"]

When something breaks in production, gather context fast and structured.

Step 1: Situational Awareness (30 seconds)

  • What's broken? (endpoint, feature, service)
  • When did it start? (timestamp or "since deploy X")
  • Who reported it? (CS, user, monit

Alternatives in Development

  • Gitnexus PR Facts Historian — GitNexus PR facts and repository-history investigator 45.8k ★
  • Incident Runbook Templates — Production-ready templates for incident response runbooks covering detection, triage, mitigation, re 31.9k ★
  • Brag Spotter — Proactively scans for achievements and wins that aren't in the brag doc yet 4.6k ★

Full documentation available on GitHub

View Source Repository