incident-hotfix

What This Skill Does

The incident-hotfix skill provides a rigorous, standardized framework for OpenClaw agents to manage production incidents. It moves beyond simple debugging by automating the creation of secure hotfix branches, enforcing strict evidence collection, and ensuring that every code change is paired with a verified rollback plan. By integrating directly into your repository's workflow via specific CLI scripts, the agent maintains a high level of accountability and safety during high-stress production outages.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/broedkrummen/incident-hotfix Ensure your agent has the necessary permissions to execute shell scripts and write to the repository's docs/ and hotfix/ directory structures.

Use Cases

• Emergency Bug Squashing: When a regression hits production and requires immediate but surgical remediation.
• Evidence-Based Debugging: Automating the collection of system snapshots and log outputs to ensure a clear audit trail for compliance.
• Controlled Patching: Managing the lifecycle of a fix from reproduction to merge, ensuring the codebase remains stable while addressing critical issues.
• Post-Incident Analysis: Automatically generating tracking documents that bridge the gap between technical hotfixes and long-term infrastructure improvements.

Example Prompts

1. "OpenClaw, we have a critical memory leak in the production auth service. Please initiate a hotfix using incident ID INC-8821 and gather the current evidence bundle."
2. "I need you to verify the reproduction steps for the INC-9902 hotfix branch. Please create a minimal failing test case and ensure it catches the error before we apply the patch."
3. "The fix for INC-4421 is ready. Please generate the final ROLLBACK.md document and prepare the summary for the PR, including all evidence captured in the docs folder."

Tips & Limitations

• Containment First: Prioritize containment over clean architecture. If you cannot find the root cause quickly, aim for a patch that stops the bleeding while maintaining the system state.
• Verification is Mandatory: Never attempt to merge a hotfix without successfully running the local reproduction test.
• Scope Creep: Avoid the urge to refactor during a hotfix. Keep changes strictly limited to the issue at hand to minimize risk.
• Documentation Integrity: Always keep the TIMELINE.md updated in real-time; it is the primary source of truth for postmortem reviews.