Triages failing GitHub Actions runs, hardens Dockerfiles, pre-flights Kubernetes manifests before they reach the cluster, and drafts blameless postmortems from incident evidence
3 on GitHubby Sigistryv1.0.0MITupdated yesterdaydevops
/
Plugin ci-incident-medic from marketplace sigistry in sigistry/marketplace. Commands read from the repo's manifest — yesterday.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
What it installs
Skills (4)
dockerfile-smells
This skill should be used when the user mentions "Dockerfile", "docker image size", "container security", "multi-stage build", "distroless", "run as root", "docker layer caching", or is reviewing/optimizing a container image. It provides a catalog of Dockerfile anti-patterns and the hardening princi
gha-failure-taxonomy
This skill should be used when the user mentions "github actions failing", "CI failure", "workflow failed", "actions permission denied", "secret not found", "matrix", "cache miss", "GITHUB_TOKEN", "pipeline red", or is diagnosing a red GitHub Actions run. It provides a taxonomy of failure classes wi
incident-response
This skill should be used when the user mentions "postmortem", "incident", "root cause analysis", "blameless", "severity", "SEV1", "on-call", "RCA", or "outage", or is writing up an incident. It provides a blameless postmortem methodology, a severity model, and reliability metric definitions.
k8s-manifest-validation
This skill should be used when the user mentions "kubernetes manifest", "k8s yaml", "deployment not ready", "pod crashloop", "resource limits", "liveness readiness probe", "securityContext", or "helm values", or is validating manifests before deploy. It provides the silent failure modes of K8s manif
Slash commands (5)
/ci-incident-medic:dockerfile-optimize
Analyze and harden a Dockerfile for size, security, and build speed
/ci-incident-medic:gha-triage
Triage a failing GitHub Actions run and produce the exact corrected YAML
/ci-incident-medic:k8s-preflight
Validate Kubernetes manifests before deploy with a gated PASS/WARN/FAIL checklist
/ci-incident-medic:postmortem
Draft a blameless postmortem from incident evidence
/ci-incident-medic:workflow-review
Proactively review a GitHub Actions workflow for security and speed
Subagents (3)
ci-failure-triager
Use this agent when a CI pipeline is failing and you need the root cause and exact fix, across GitHub Actions, GitLab CI, or CircleCI. Trigger on "CI is red", "workflow failed", "pipeline broken", "why did the build fail", "actions permission denied", "secret not found", or a pasted CI log. Examples
dockerfile-hardener
Use this agent when a Dockerfile should be made smaller, safer, and faster, multi-stage build, non-root user, pinned base, cache-friendly ordering, and a matching .dockerignore. Trigger on "harden my Dockerfile", "reduce image size", "container runs as root", "add multi-stage build", or a scanner fl
postmortem-writer
Use this agent when an incident is resolved and you need a blameless postmortem assembled from raw evidence. Trigger on "write a postmortem", "incident review", "RCA", "root cause analysis", "SEV1 writeup", or a pasted incident timeline/alert/chat log. Examples:
Monitoring and evaluation jobs on your project folder: twelve job skills (evaluation questions, question-method alignment, evaluation TOR drafts, indicator reference sheets, measurement feasibility, M&E plan drafts, progress evidence, findings to actions, results chain alignment, sampling plans, data quality assessment plans, baseline planning), three workflow packs and nineteen commands that cross-reference logframes, M&E plans, proposals, reports and TORs and write editable Markdown with source traceability.
Builds up to a goal in a field you have no expertise in: splits it into the foundations that goal actually needs, mobilizes what you already hold, learns what is missing, and leaves every solved path behind for the next goal. Nothing is called done until a check passes.
Goes past detecting accessibility and localization issues to fixing them: cross-element ARIA and keyboard-focus remediation, color-contrast rewrites, hardcoded-string extraction, ICU MessageFormat correctness, and RTL readiness
A repo-native toolchain for LLM apps: scaffolds eval suites, red-teams for prompt injection, hardens structured-output reliability, and audits token cost, riding promptfoo/DeepEval/Pydantic rather than replacing them
Owns everything around the diff: craft Conventional Commits and PR descriptions, recommend the right semver bump by reasoning about behavioral breaking changes, assemble changelogs from messy history, and guide merge-conflict resolution, rebase planning, and git-history archaeology
Transform Claude into an Azure expert. This plugin integrates the Azure MCP server and specialized Azure skills to move beyond generic advice. It enables Claude to perform real-world tasks: listing resources, validating deployments, diagnosing infrastructure issues, and optimizing costs across 50+ Azure services.
Work with incident.io from Claude: respond to and investigate incidents, check on-call schedules and escalations, and author the runbooks, skills and architecture docs that incident.io investigations draw on. Bundles the official incident.io MCP server (OAuth on first use).
67 specialized skills for full-stack development: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 8 backend frameworks, 7 frontend/mobile, plus infrastructure, DevOps, security, and testing skills. Includes 9 project workflow commands for epic planning, discovery, execution, and retrospectives.
67 skills · 10 commands
Jeffallan/claude-skills 12,345
Maintain ci-incident-medic?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.