mcpField
I
incident-response-smart-fix

incident-response-smart-fix

github.com/sickn33Development48.7k169 installsUpdated today
Repository

About incident-response-smart-fix

incident-response-smart-fix is a multi-agent skill for diagnosing and fixing production issues, intended for development teams handling systematic investigations. It structures work into analysis, root-cause investigation, implementation, and verification, with an emphasis on testing and recurrence prevention.

Key features

  1. 01Organize issue handling in four phases
  2. 02Analyze errors, logs, and observability data
  3. 03Investigate root causes and introducing changes
  4. 04Implement minimal fixes with tests
  5. 05Run regression, performance, and security checks

Use cases

  1. 01Find the cause of a production incident
  2. 02Trace the change that introduced a regression
  3. 03Coordinate specialist agents on cross-system fixes
  4. 04Verify fixes and reduce recurrence risk

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill incident-response-smart-fix

After installing, type/incident-response-smart-fixin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

Intelligent Issue Resolution with Multi-Agent Orchestration

[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and resolve production issues. The intelligent debugging strategy combines automated root cause analysis with human expertise, using modern 2024/2025 practices including AI code assistants (GitHub Copilot, Claude Code), observability platforms (Sentry, DataDog, OpenTelemetry), git bisect automation for regression tracking, and production-safe debugging techniques like distributed tracing and structured logging. The process follows a rigorous four-phase approach: (1) Issue Analysis Phase - error-detective and debugger agents analyze error traces, logs, reproduction steps, and observability data to understand the full context of the failure including upstream/downstream impacts, (2) Root Cause Investigation Phase - debugger and code-reviewer agents perform deep code analysis, automated git bisect to identify introducing commit, dependency compatibility checks, and state inspection to isolate the exact failure mechanism, (3) Fix Implementation Phase - domain-specific agents (python-pro, typescript-pro, rust-expert, etc.) implement minimal fixes with comprehensive test coverage including unit, integration, and edge case tests while following production-safe practices, (4) Verification Phase - test-automator and performance-engineer agents run regression suites, performance benchmarks, security scans, and verify no new issues are introduced. Complex issues spanning multiple systems require orchestrated coordination between specialist agents (database-optimizer → performance-engineer → devops-troubleshooter) with explicit context passing and state sharing. The workflow emphasizes understanding root causes over treating symptoms, implementing lasting architectural improvements, automating detection through enhanced monitoring and alerting, and preventing future occurrences through type system enhancements, static analysis rules, and improved error handling patterns. Success is measured not just by issue resolution but by reduced mean time to recovery (MTTR), prevention of similar issues, and improved system resilience.]

Use this skill when

  • Working on intelligent issue resolution with multi-agent orchestration tasks or workflows
  • Needing guidance, best practices, or checklists for intelligent issue resolution with multi-agent orchestration

Do not use this skill when

  • The task is unrelated to intelligent issue resolution with multi-agent orchestration
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported