pelizzai-recovery

Diagnose Git working tree divergences and guide safe restoration workflows.

Updated Jun 26, 2026

Search Tags:#git #workflow #safety #recovery #reconciliation #version-control

Ready to run

npx skills add https://github.com/rpelizza/PelizzAI --skill pelizzai-recovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pelizzai-recovery
Source: https://github.com/rpelizza/PelizzAI/tree/main/.agents/skills/pelizzai-recovery
Command: npx skills add https://github.com/rpelizza/PelizzAI --skill pelizzai-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves discrepancies between an AI agent's task record and the actual Git repository state, preventing data loss or corrupted worktrees after crashes or context switches.

Core Features & Use Cases

Safe Diagnosis: Performs read-only analysis of Git status, branches, and worktrees to identify the cause of divergence.
Risk Mitigation: Prevents destructive operations like forced resets or deletions by enforcing a mandatory recovery gate and requiring explicit user confirmation.
Use Case: When an agent crashes mid-task and you resume in a dirty working tree, this skill helps you safely reconcile your progress without losing uncommitted work or breaking the project history.

Quick Start

Run the pelizzai-recovery skill to diagnose the current Git divergence and propose a safe path forward.

Frequently Asked Questions about pelizzai-recovery

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

FAQPage Schema

How do I reconcile a dirty Git working tree after an agent crash?▼

To reconcile a dirty Git working tree after a crash, run a safe diagnosis to analyze repository status and identify recovery points. This guides you through restoration workflows while gating destructive operations behind explicit confirmation to prevent data loss.

What is the safest way to recover uncommitted Git changes without losing data?▼

The safest way to recover uncommitted Git changes is to perform read-only analysis of your branches and worktrees first. This identifies the cause of divergence and enforces a mandatory recovery gate before any destructive operations like forced resets are executed.

How do I diagnose Git state divergences between task records and repository status?▼

Diagnosing Git state divergences involves performing read-only analysis of your working tree, branches, and worktrees. This identifies the exact cause of the discrepancy between execution records and repository states to propose a safe restoration path forward.

Can I prevent forced resets or deletions during Git version-control recovery?▼

Yes, you can prevent forced resets or deletions during Git recovery by enforcing a mandatory recovery gate. This risk mitigation strategy requires explicit user confirmation and verified return points before executing any destructive operations.

When should I use a guided Git reconciliation workflow for my project history?▼

You should use a guided Git reconciliation workflow when an agent crashes mid-task and you resume in a dirty working tree. It safely reconciles your progress and prevents breaking project history after interruptions or context switches.