gk-incident

Orchestrate incident response workflows with severity triage and postmortem documentation.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/gkganesh12/gk-stack --skill gk-incident
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gk-incident
Source: https://github.com/gkganesh12/gk-stack/tree/main/skills-extra/gk-incident
Command: npx skills add https://github.com/gkganesh12/gk-stack --skill gk-incident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the chaos of production outages by providing a structured, mitigation-first playbook that ensures incidents are handled safely, logged accurately, and followed by blameless postmortems.

Core Features & Use Cases

  • Mitigation-First Workflow: Prioritizes safe paths back to green (reverts, flag flips) before diagnosing root causes.
  • Automated Timeline Logging: Automatically timestamps every action and decision into a dedicated incident directory.
  • Postmortem Generation: Converts the incident timeline into a structured postmortem report that feeds directly into Learned Rules.
  • Use Case: When a production service experiences a spike in error rates, use this skill to triage the severity, draft client communications, and track mitigation steps without losing focus on the incident clock.

Quick Start

Trigger the incident response workflow by stating the current issue such as production is down and we need to start the triage process.

Frequently Asked Questions about gk-incident

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a structured incident response workflow for a production outage?

To run a structured incident response workflow, trigger the triage process with your issue description. The skill prioritizes safe mitigation paths like reverts and flag flips before diagnosing root causes, ensuring rapid and safe remediation.

What is a mitigation-first approach to incident triage?

A mitigation-first approach to incident triage prioritizes safe paths back to green, such as reverts and flag flips, before diagnosing root causes. This ensures production outages are handled rapidly and safely without losing focus on the incident clock.

How do I automate timeline logging during service degradation incidents?

You automate timeline logging during service degradation by using a structured incident response workflow that automatically timestamps every action and decision into a dedicated incident directory for accurate evidence capture.

Can I generate a blameless postmortem directly from an incident timeline?

Yes, you can generate a blameless postmortem directly from an incident timeline. The workflow converts logged mitigation actions and timestamped evidence into a structured report that feeds directly into Learned Rules.

Does incident response handling require specific environment setup?

Incident response handling requires adherence to the GK-Stack incident protocol for timestamped evidence capture and blameless feedback loops. No external dependencies are needed to execute the severity triage and mitigation planning workflows.

When should I not use a structured incident response workflow?

You should avoid using a structured incident response workflow for routine maintenance or non-production issues. It is specifically designed for production outages and service degradation scenarios requiring rapid, logged, and safe remediation.