Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →okhp3/okhp3-replit-repl-janitor
OverKill Hill P³ one-Repl repository cleanup workflow for safely auditing and tidying a single Replit workspace's Git checkout.
Passed 16 of 19 test cases with the skill, and 10 of 19 without it.
and 10 more in the full report
8 fixed11 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to refresh remote branch references before running our workspace audit. Should I run git fetch with the --prune flag to clear out old tracking refs immediately?
| Checked | Without skill | With skill |
|---|---|---|
| The response states that git fetch --prune must not be run during initial discovery | Missed | Passed |
| The response explains that pruning before classification destroys evidence needed to evaluate stale remote branches | Missed | Passed |
The instructions your model reads when the skill loads.
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Safely clean one Replit workspace's Git checkout without confusing generated branch names with proof, a closed pull request with a merged one, or an untidy filename with permission to rename it. The workflow is read-only first, evidence-led, and destructive only after the owner approves exact line items.
| In scope | Out of scope |
|---|---|
| One-time cleanup of one Replit checkout | Recurring maintenance; use okhp3-repository-janitor |
| Branch and PR classification against a verified base | Multi-clone reconciliation; use okhp3-repository-janitor |
| Naming and detritus audit | Structural redesign; use okhp3-repository-organizer |
| Exact, owner-approved cleanup execution | Autonomous deletion, merging, renaming, or publishing |
--fetch; it reads the
current checkout and prints JSON. Fetch separately only when network access
is appropriate. Never prune during discovery.origin/main", "closed pull request",
and "abandoned with no PR" are different states. Never substitute one for
another.subrepl-*, replit-agent, and agent/*
suggest generated work but do not prove it is safe to delete. The current
branch is never a deletion candidate.keep, merge, delete, and
review branch buckets plus file actions. Wait for explicit approval of
individual destructive lines.test cases passed, vs 10 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.