mayankit

Aiskills Incident Investigator — Development agent for Claude Code

Development community

Investigates live production incidents end to end — triages impact and start time, draws the blast radius, mitigates first to stop customer bleeding, then hypothesizes and verifies root cause with tim.

How to install Aiskills Incident Investigator

Installs to ~/.claude/agents/mayankit-aiskills-aiskills-incident-investigator.md

Terminal
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/mayankit/AISkills/HEAD/agents/aiskills-incident-investigator.md -o ~/.claude/agents/mayankit-aiskills-aiskills-incident-investigator.md

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

What Aiskills Incident Investigator does


name: aiskills-incident-investigator description: Investigates live production incidents end to end — triages impact and start time, draws the blast radius, mitigates first to stop customer bleeding, then hypothesizes and verifies root cause with timeline evidence, and guards against recurrence with a test or alarm before writing a blameless post-incident review. Invoke when an alarm fires, users report degradation in production, a recent symptom must be correlated with a deployment or confi

Alternatives in Development

  • Cross Linker — Scan recent or specified notes for missing wikilinks 4.6k ★
  • Codebase Scout — Explores codebase structure, affected files, blast radius, related tests, and local conventions for a focused 548 ★
  • Architecture Mapper — Maps all files and architectural layers that will be affected by a proposed change 160 ★

Full documentation available on GitHub

View Source Repository