recommend-fixes

Validate incident fix options against historical remediation patterns.

13|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/unblocked/cookbook --skill recommend-fixes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recommend-fixes
Source: https://github.com/unblocked/cookbook/tree/main/recipes/recommend-fixes
Command: npx skills add https://github.com/unblocked/cookbook --skill recommend-fixes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides structured, prioritized fix recommendations for incidents by validating candidate solutions against historical patterns and prior fixes, ensuring you avoid regressive changes.

Core Features & Use Cases

  • Historical validation: checks past remediation PRs and precedents to filter out ineffective fixes.
  • Tiered recommendations: delivers Immediate mitigation, Root cause fix, and Prevention options with context.
  • PR-ready outputs: includes actionable details, risk, rollback, and deployment context for remediation PRs.

Quick Start

Run the incident prompt through context_research to generate a prioritized fix plan.

Frequently Asked Questions about recommend-fixes

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

FAQPage Schema
How do I find validated incident remediation patterns to avoid regressive fixes?

Validated incident remediation patterns are identified by comparing candidate solutions against historical fix precedents and past remediation PRs. This filters out ineffective options and ensures you avoid regressive changes during incident response.

What's the best way to structure incident fix recommendations with rollback planning?

Incident fix recommendations are structured into tiered options: immediate mitigation, root cause fix, and prevention. Each tier includes actionable details, risk assessment, rollback planning, and deployment context for PR-ready outputs.

Can I generate PR-ready context for incident remediation across different services?

Yes, PR-ready context is generated across teams and services by producing tiered recommendations with structured outputs and templates. This satisfies requirements for historical validation, risk assessment, rollback planning, and documentation.

How do I confirm if a suspected root cause fix matches historical remediation patterns?

Suspected root cause fixes are validated by checking past remediation PRs and precedents. This historical pattern matching confirms whether the candidate solution aligns with previously successful incident remediation efforts.

Does this incident response approach work when root causes are only suspected and not confirmed?

Yes, this approach applies to incident response workflows where root causes are either confirmed or suspected. It compares candidate solutions against historical remediation patterns to produce validated, tiered fix recommendations regardless of confirmation status.

Why should I use historical validation for incident fixes instead of applying direct patches?

Historical validation checks past remediation PRs and precedents to filter out ineffective fixes before deployment. This prevents regressive changes by ensuring candidate solutions are validated against proven historical patterns rather than applied directly.