continue-crash

Reconstruct task context from Git state and TODO files after a crash.

9|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/wpfleger96/ai-rules --skill continue-crash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continue-crash
Source: https://github.com/wpfleger96/ai-rules/tree/main/src/ai_rules/config/skills/continue-crash
Command: npx skills add https://github.com/wpfleger96/ai-rules --skill continue-crash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continues work after a session crash by reconstructing task context and guiding a smooth recovery.

Core Features & Use Cases

  • Rebuilds task context from recent commits, Git status, and planning notes to resume work after an interruption.
  • Generates a fresh action plan and updates TODOs to reflect the current state, preventing duplicated effort.
  • Provides safe, guided steps to re-engage tasks across sessions and restore momentum with minimal loss.

Quick Start

Review the current repository state and TODO/PLAN files to regenerate a resume plan and continue the interrupted task.

Frequently Asked Questions about continue-crash

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

FAQPage Schema
How do I recover task context and resume work after a session crash?

To recover task context after a session crash, reconstruct your work state by analyzing recent git commits, current Git status, and existing planning notes to regenerate an actionable resume plan.

What is the best way to restore an interrupted development task without duplicating effort?

Restoring an interrupted task requires regenerating an action plan from recent commits and TODO files, which updates your current state and prevents duplicated effort when re-engaging across sessions.

How do I rebuild a project plan from git history and TODO files?

Rebuilding a project plan from git history involves reviewing recent commits and TODO files to extract previous plan directions, allowing you to generate a fresh action plan reflecting the current repository state.

Can I use git context to safely resume tasks across multiple sessions?

Yes, you can use git context to safely resume tasks across sessions by enforcing contextual recovery, which provides guided steps to re-engage interrupted work and restore momentum with minimal data loss.

Why do I need to review the repository state before generating a resume plan?

Reviewing the repository state is necessary before generating a resume plan because it captures the latest git status and planning notes, ensuring the regenerated task context accurately reflects your current development progress.

What should I do if my TODO files and recent git commits are out of sync after an interruption?

If TODO files and recent git commits are out of sync, you should regenerate your action plan by comparing the planning notes against the actual git state to safely guide task re-engagement and prevent duplicated effort.