incident-response

Convert production failure logs into a regression test and surgical code fix.

Updated Mar 8, 2026

Search Tags:#debugging #TDD #incident response #regression testing #hotfix #post-deploy

Ready to run

npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill incident-response-luyzkk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/incident-response
Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill incident-response-luyzkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents fragile, unverified hotfixes by enforcing a disciplined post-deploy incident workflow that starts with raw logs and ends with a regression-tested commit.

Core Features & Use Cases

Logs-first triage: Uses literal raw logs to form hypotheses and avoids “guessing” before evidence.
Regression test before fix: Requires a failing regression test that reproduces the incident condition before any code changes.
Surgical fix + hardening: Implements the minimal change to make the test suite pass, then adds targeted hardening to close nearby gaps.
Use case: When an endpoint suddenly returns 500 in production due to a specific payload shape or edge case, this skill guides you through root-cause hypothesis, reproducing it in a test, fixing it, and documenting the prevention.

Quick Start

Paste your production logs or incident description and ask the AI to walk you through the incident-response flow from hypothesis to regression-tested fix.

Frequently Asked Questions about incident-response

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

FAQPage Schema

How do I fix a production 500 error without guessing the root cause?▼

Production 500 errors are fixed by ingesting raw logs to form an evidence-based hypothesis, writing a failing regression test that reproduces the edge case, and applying a surgical code correction to verify the fix.

What is the best way to reproduce a runtime crash before deploying a hotfix?▼

Reproducing a runtime crash requires writing a regression test that deliberately fails under the specific incident condition, ensuring the hotfix is validated against actual failure logs before any code changes are applied.

How do I create a regression test for an edge case failure found post-deploy?▼

Post-deploy edge case failures are reproduced by parsing production logs to identify the exact payload shape, then writing a test that fails against current code before implementing a minimal change to make it pass.

Does incident response debugging require raw logs before writing a fix?▼

Yes, disciplined incident response requires raw log ingestion first to form a hypothesis, preventing unverified hotfixes by ensuring evidence-based validation precedes any code correction or hardening.

What should a post-incident commit message include to document a hotfix?▼

A structured post-incident commit should include the root-cause analysis, reference to the regression test that reproduced the failure, and documentation of any observability hardening applied to close nearby gaps.

When should I avoid a minimum-change approach to fixing production incidents?▼

Minimum-change implementation is standard for surgical fixes, but you should add targeted hardening to close nearby gaps after the regression test passes, ensuring observability and preventing similar edge-case failures.