Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for OSS maintainers cleaning up after agent-generated commits, teams rebasing AI-generated work onto clean commit histories, and engineers migrating repos between author identities.
Who should use it
Who should skip it
Avoid running TheRealYT/git-knife in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
TheRealYT/git-knife is tracked by RepoRadar as a developer tool in the Developer Tooling section. First seen 2026-08-12; the source record was last checked on 2026-08-12. The current verdict is 'try now' with a Silver tier and easy setup difficulty. The standout signals for TheRealYT/git-knife are workflow potential (9.7) and novelty (9.0), while maturity (6.0) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The TheRealYT/git-knife record combines a 8.2/10 composite score with separate popularity (2.2), risk (medium), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It is a destructive git-history editor; always test against a non-production repo and a force-pushed branch with a backup before adopting as the default; License field is null on the GH API snapshot; reviewer must fetch raw LICENSE@main before committing the card to confirm the redistribution posture.