investigate-incident

Stars2

Forks1

UpdatedMarch 11, 2026 at 22:49

Investigate a cluster incident by systematically checking recent activity, failed operations, and resource changes. Use when the user reports something is broken, asks "what happened", mentions an outage, incident, or error, or wants to understand recent cluster changes.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

datum-cloud

datum-cloud/claude-code-plugins

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

More from this repository

same repository

github-conventions

datum-cloud/claude-code-plugins

Covers GitHub conventions for pull requests, issues, and comments including linking, language style, formatting, and callout syntax. Use when creating PRs, writing issues, or posting comments on Datum Cloud repositories.

2026-07-092

changelog-entry

datum-cloud/claude-code-plugins

Turn raw engineering notes, PR/issue links, commit messages, or a one-line feature description into a changelog entry for Datum Cloud's GitHub Discussions Changelog category: a benefit-led title plus a markdown body, drafted for users and ready to hand off for final capture and publish. Use when someone says "write a changelog entry", "announce this in the changelog", or "post this to the changelog discussions" — this is the community-facing changelog POST, not the Keep a Changelog release file (that lives in `gtm-templates`).

2026-07-092

gtm-templates

datum-cloud/claude-code-plugins

Provides templates for go-to-market communications including blog posts, changelogs, social media, and enablement briefs. Use when writing launch announcements or marketing content.

2026-07-092

release

datum-cloud/claude-code-plugins

Create a new GitHub release. Verifies CI is green on the release commit and refreshes the third-party NOTICE file before tagging, determines the next version from the latest tag, summarizes merged PRs since the last release, drafts release notes in the established style, and publishes via gh release create. Works for any datum-cloud service repository.

2026-07-012

agpl-compliance

datum-cloud/claude-code-plugins

Scan a project repository for strict AGPL-3.0 license compliance across Go, Rust, and JavaScript/React codebases. Use this skill whenever the user asks to check, audit, verify, or enforce AGPL license compliance on a project, repo, or codebase. Triggers on phrases like "check agpl compliance", "audit license headers", "is this project agpl compliant", "scan for license headers", "check my license files", "agpl audit", or any request involving ensuring a project is properly licensed under AGPL. Always use this skill — don't wing AGPL compliance checks from general knowledge.

2026-05-222

operational-review

datum-cloud/claude-code-plugins

Covers producing weekly operational reports for the Datum AI Edge. Use when asked for an ops review, traffic report, latency analysis, provisioning report, or edge performance summary. Guides metric queries, anomaly detection, and publishing to datum-cloud/engineering.

2026-04-152

name	investigate-incident
description	Investigate a cluster incident by systematically checking recent activity, failed operations, and resource changes. Use when the user reports something is broken, asks "what happened", mentions an outage, incident, or error, or wants to understand recent cluster changes.
context	fork
agent	incident-investigator

name	investigate-incident
description	Investigate a cluster incident by systematically checking recent activity, failed operations, and resource changes. Use when the user reports something is broken, asks "what happened", mentions an outage, incident, or error, or wants to understand recent cluster changes.
context	fork
agent	incident-investigator