skevy/git-deps — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2020-04-29
Figure out exactly which commits you need to cherry-pick when porting a feature between branches.
Reorganize a messy series of commits into clean, independent topics before opening a pull request.
Automatically identify and squash fixup commits into the commits they actually fix.
| skevy/git-deps | 0xkinno/neuralvault | 0xmayurrr/ai-contractauditor | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | — | TypeScript | TypeScript |
| Last pushed | 2020-04-29 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | moderate | hard | easy |
| Complexity | 2/5 | 4/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Command-line tool that runs against an existing git repository's history.
A tool that analyzes a git repository to figure out which commits depend on which earlier commits, based on shared lines of code they touch.
Dormant — no commits in 2+ years (last push 2020-04-29).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.