crash-recovery

To recover your development session state after a crash, this Skill reconstructs your working environment by analyzing git status, scratchpad artifacts, and session history to identify in-progress tasks and generate handoff notes for seamless resumption.

Creating a checkpoint before risky git operations involves saving your current working state. This Skill manages checkpoint creation automatically, capturing your environment context so you can safely execute commands and restore the exact state if a failure occurs.

Session state reconstruction works by extracting uncommitted changes from git status and combining them with scratchpad artifacts and session history. This process rebuilds the context lost during an unexpected termination, allowing you to resume development seamlessly.

Yes, you can generate handoff notes for task resumption after a context loss. This Skill creates clear, actionable instructions detailing where you left off, enabling seamless continuation of your development tasks without manually retracing your steps.

Yes, crash recovery works without external dependencies. This Skill relies solely on your existing development environment artifacts, specifically git status, scratchpad files, and session history, to reconstruct your state and generate recovery notes.

You need to reconstruct session state for seamless continuation whenever you experience unexpected context resets, IDE crashes, or terminations. This Skill ensures your work is not lost by automatically restoring the environment and identifying in-progress tasks.