skills.rest
OKHP3
OKHP3COMMUNITY
Explore all skills by this author →
WebsiteGitHub

okhp3-replit-repl-janitor

Audit and clean one Replit Git checkout with evidence-led branch classification and owner-approved execution.

Updated Aug 17, 2026
Search Tags:#git#pull requests#naming conventions#code hygiene#branch cleanup#replit#repository audit
One-click install
npx skills add https://github.com/OKHP3/telling-forward --skill okhp3-replit-repl-janitor-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-replit-repl-janitor
Source: https://github.com/OKHP3/telling-forward/tree/main/.agents/skills/okhp3-replit-repl-janitor
Command: npx skills add https://github.com/OKHP3/telling-forward --skill okhp3-replit-repl-janitor-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Replit workspaces accumulate stale subrepl-* and agent/* branches, closed-but-unmerged pull requests, inconsistent filenames, and detritus folders like attached_assets/. Deleting by name pattern or pruning early destroys evidence and risks losing unmerged work. This Skill provides a read-only-first, evidence-led workflow that classifies every branch and file action before anything destructive happens. ## Core Features & Use Cases - Branch and PR classification: Sorts every non-current branch into keep, merge, delete, or review buckets using verified Git facts and GitHub CLI pull-request state, never inferring abandonment from a failed lookup. - Naming and detritus audit: Flags kebab-case violations while preserving structural exceptions (PascalCase .tsx components, camelCase useFoo.ts hooks, root governance files, tool-required and web-standard names), and triages detritus folders before disposal. - Verified safe execution: Runs a pre-delete check that compares the reviewed branch head SHA against the freshly read tip, emits remote-first deletion commands, and refuses early pruning, force-pushes, or main rewrites. - Use Case: A user asks to "decrapify this Repl" with dozens of subrepl-* branches. The Skill runs the bundled audit script, resolves PR state with gh, presents an exact keep/merge/delete/review plan, and executes only the line items the owner explicitly approves. ## Quick Start Ask the agent to audit this Repl's branches, pull requests, filenames, and detritus folders and present a cleanup plan before deleting anything.

Frequently Asked Questions about okhp3-replit-repl-janitor

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

FAQPage Schema
How do I safely delete old Replit branches like subrepl-* or agent/*?▼

Treat generated branch names as hints, not proof. Classify each branch by checking whether it is merged into the base ref and resolving its pull-request state with gh pr list --head, then delete only branches verified merged or explicitly abandoned by the owner.

How to audit a Git repository for stale branches and bad filenames?▼

Run the bundled audit-repo.py script with --root and --base flags; it prints a read-only JSON report of branch facts, kebab-case naming violations, and detritus folders. It never deletes, renames, prunes, or fetches unless --fetch is explicitly passed.

What is the difference between a closed PR and a merged branch?▼

A closed pull request, a branch merged into origin/main, and abandoned work with no PR are three distinct states. Deletion is only justified by verified merge into the base or owner-confirmed abandonment, never by closure alone.

Does the audit script work on repositories outside Replit?▼

The audit script works on any Git work tree with a verifiable base ref, but the workflow, branch patterns, and detritus rules are tuned for a single Replit checkout. Recurring maintenance or multi-clone reconciliation is out of scope.

Why should I avoid git fetch --prune before cleaning branches?▼

Pruning before classification destroys evidence about stale remote-tracking branches, making it impossible to distinguish merged, closed, and abandoned states. Fetch without --prune during discovery and prune only after every stale branch is classified.

When should I not use this cleanup workflow?▼

Avoid it for recurring repository maintenance, multi-repository or multi-clone reconciliation, and structural taxonomy redesign. It also never performs autonomous merges, deletions, force-pushes, main rewrites, or stash and archive-ref deletion.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

git-remote

Manage git remotes and synchronize local branches with remote refs.

Official
Intermediate
davepoondavepoon
3.4k

check

Run CIAgent regression checks and interpret results after changing an AI agent's code, prompts, or knowledge base.

Community
Intermediate
ConductionNLConductionNL
1

report-out

Generates Dutch Slack reports from git and GitHub activity scans.

Official
Advanced
evolution-foundationevolution-foundation
520

schedule-task

Create one-off scheduled tasks for skills, prompts, or scripts at exact future times.

Official
Intermediate