recover

Name: recover
Availability: InStock
Author: kelsi-andrewss

Detect and reconcile Git worktree and database inconsistencies.

1|Updated Feb 21, 2026

Search Tags:#pipeline #git-worktree #recover #mismatch-detection #story-management #db-sync

Ready to run

npx skills add https://github.com/kelsi-andrewss/claude-multi-agent-pipeline --skill recover

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: recover
Source: https://github.com/kelsi-andrewss/claude-multi-agent-pipeline/tree/main/skills/recover
Command: npx skills add https://github.com/kelsi-andrewss/claude-multi-agent-pipeline --skill recover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-reference git worktree state against the DB to find mismatches, detect orphaned worktrees, stale DB records, and stories stuck in incorrect states.

Core Features & Use Cases

Cross-reference Git worktree layout with the pipeline DB to surface inconsistencies across epics and stories.
Detect orphaned worktrees, in-progress stories without a corresponding worktree, and stale database entries, then propose safe remediation actions.
Support safe mutations by guiding users to update the DB via pm_update_story or perform git work tree removals with explicit user confirmation.

Quick Start

Run a scan to compare git worktrees under .claude/worktrees/story/ with active DB stories, review mismatches, and apply safe updates.

Frequently Asked Questions about recover

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

FAQPage Schema

How do I detect orphaned git worktrees and stale database records?▼

To detect orphaned git worktrees and stale database records, run a scan that cross-references your worktree layout under .claude/worktrees/story/ against active pipeline DB stories to surface mismatches and inconsistencies.

Why does my pipeline database show a story as in-progress when the git worktree is missing?▼

A pipeline database may show a story as in-progress without a corresponding git worktree due to unsynced state mutations; scanning worktrees against DB records detects this mismatch and proposes safe updates.

How do I safely remove orphaned git worktrees without breaking the pipeline database?▼

Orphaned git worktrees are safely removed by flagging them for deletion during a reconciliation scan, but the system requires explicit user confirmation before executing any worktree removal mutations.

Can I automatically update the pipeline database to match git worktree state?▼

You cannot automatically mutate the pipeline database; the system proposes safe remediation actions and guides you to apply updates via pm_update_story, ensuring deliberate state synchronization.

What is the best way to sync git worktree state with a story management database?▼

The best way to sync git worktree state with a story management database is a full lifecycle reconciliation scan that identifies mismatches across epics and stories, then proposes safe DB updates and worktree removals.