How dudesquad999/git-panic works
git-panic is a local Git recovery CLI: users inspect HEAD reflog entries, search them or browse an interactive timeline, then preview and optionally create a branch for a selected commit. The graph separates command routing, reflog discovery, search, TUI inspection, and recovery. README documents these workflows and the JSON interface; the sampled implementation is one file, so several components share its path. No remote Git service is involved.
Main entry points: main.rs Command routing
Components 8
CLI workflows
- Command routing
src/main.rs - HEAD reflog reader
src/main.rs - Literal search
src/main.rs - Interactive timeline
src/main.rs - JSON responses
src/main.rs
Commit recovery
- Branch recovery
src/main.rs
Other components
- Developer or assistant
- Local Git repository
Connections 9
- Developer or assistant → Command routing: runs command
README.md - Command routing → HEAD reflog reader: reads timeline
README.md - HEAD reflog reader → Local Git repository: reads HEAD reflog
src/main.rs - Command routing → Literal search: routes query
README.md - Command routing → Interactive timeline: opens timeline
README.md - Literal search → JSON responses: formats results
README.md - Command routing → Branch recovery: routes recovery
README.md - Branch recovery → Local Git repository: validates and creates branch
README.md - Branch recovery → JSON responses: formats response
README.md