awf-rollback

Diagnose deployment failures and restore code to a stable state.

Updated Jul 6, 2026

Search Tags:#git #debugging #deployment #rollback #recovery #emergency

Ready to run

npx skills add https://github.com/buiminhduc23011/awf-for-codex --skill awf-rollback

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: awf-rollback
Source: https://github.com/buiminhduc23011/awf-for-codex/tree/main/skills/awf-rollback
Command: npx skills add https://github.com/buiminhduc23011/awf-for-codex --skill awf-rollback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, calm, and systematic approach to recovering from deployment failures or accidental code changes, preventing panic and minimizing downtime.

Core Features & Use Cases

Damage Assessment: Guides the user through a diagnostic process to identify the root cause of the failure.
Flexible Recovery Options: Offers specific file restoration, full session rollback, or manual debugging paths.
Use Case: If a recent code change breaks the application, the user can invoke this skill to revert specific files or the entire session to a stable state.

Quick Start

Invoke the rollback workflow by typing awf-rollback to begin the emergency recovery process for your current session.

Frequently Asked Questions about awf-rollback

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

FAQPage Schema

How do I revert code changes after a failed deployment?▼

To revert code changes after a failed deployment, you can use a systematic rollback framework to restore application stability. It guides you through diagnostic assessment and offers specific file-level restoration or full session rollback paths to safely recover.

What is the best way to restore files during emergency deployment recovery?▼

The best way to restore files during emergency deployment recovery is using a structured framework that offers flexible options. You can choose specific file-level restoration or a broader session-wide rollback to ensure safe state transitions and minimize downtime.

Does this rollback framework support post-recovery testing protocols?▼

Yes, the rollback framework supports post-recovery testing protocols. It ensures safe state transitions by facilitating systematic verification after you apply multi-path recovery strategies, confirming application stability before completing the process.

Can I use a manual debugging path instead of a full session rollback?▼

Yes, you can use a manual debugging path instead of a full session rollback. The framework offers flexible recovery options, allowing you to choose between file-level restoration, complete session rollbacks, or manual debugging based on your diagnostic assessment.

When do I need a systematic recovery framework for broken code changes?▼

You need a systematic recovery framework for broken code changes when a recent deployment breaks your application. It provides a calm, structured approach to perform diagnostic assessment, execute rollbacks, and prevent panic during emergency recovery.

What are the limitations of using emergency rollback for failed deployments?▼

Emergency rollback for failed deployments relies on systematic verification and diagnostic assessment to ensure safe state transitions. Limitations include needing accurate root cause identification before executing file-level restoration or session-wide rollbacks to avoid further application instability.