physical-verification-failure-recovery

Name: physical-verification-failure-recovery
Availability: InStock
Author: Shichiyou

Reconcile git status discrepancies by verifying and correcting the index.

Updated Aug 27, 2026

Search Tags:#git #debugging #verification #diagnostics #recovery #version-control

Ready to run

npx skills add https://github.com/shichiyou/hermes-agent-001 --skill physical-verification-failure-recovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: physical-verification-failure-recovery
Source: https://github.com/shichiyou/hermes-agent-001/tree/main/.devcontainer/hermes-backup/skills/.archive/physical-verification-failure-recovery
Command: npx skills add https://github.com/shichiyou/hermes-agent-001 --skill physical-verification-failure-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The protocol provides a structured approach to recover from situations where tool outputs claim success but the repository's git status shows modifications, ensuring you can locate, verify, and reconcile discrepancies.

Core Features & Use Cases

Stop progress and prohibit destructive actions until the inconsistency is understood.
Diagnostic Probe: examine git status, check for hidden .git artifacts, and verify whether .git is a directory or a file.
Truth-Based Correction: re-align the index with the filesystem by selectively staging problematic paths and re-checking until the working tree is clean.
Verification and recovery use-cases: applicable to any directory or project where AI-assisted steps reported completion but physical state disagrees.

Quick Start

Follow the protocol immediately when a mismatch is detected between completion claims and the repository's state.

Frequently Asked Questions about physical-verification-failure-recovery

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

FAQPage Schema

How do I fix git status showing uncommitted changes when task outputs claim completion?▼

Git status discrepancies are fixed by probing the working tree for divergent changes, selectively staging problematic paths, and re-aligning the index until the filesystem matches the claimed completion state. This enforces deterministic recovery steps with explicit verification before resuming.

Why does my repository have modifications after AI-assisted steps report success?▼

Repository modifications occur when ghost completions claim success but the physical git state disagrees. A diagnostic probe examines git status, checks for hidden .git artifacts, and verifies whether .git is a directory or a file to locate the inconsistency.

What is the best way to recover a clean working tree when the git index contradicts the filesystem?▼

Recovering a clean working tree requires truth-based correction that selectively stages problematic paths and re-checks until the working tree is clean. This approach stops progress and prohibits destructive actions until the inconsistency is understood.

Can I use this recovery protocol on any directory with hidden git artifacts?▼

The protocol applies to any directory or project where AI-assisted steps reported completion but physical state disagrees. It locates divergent changes across the suspected directory and verifies with git status and ls -la before correcting the index.

What should I do before resuming work after a git verification failure?▼

Before resuming work after a git verification failure, you must apply explicit verification steps to ensure a clean state. The protocol enforces safe interaction with git and prohibits destructive actions until the discrepancy between completion claims and repository status is fully reconciled.