okhp3-repository-organizerlisted

OverKill Hill P³ repository organizer for content-first Git repositories. Use when a local Git repository grew organically from a folder and needs an evidence-based profile, purpose summary, classification, cross-platform naming cleanup, folder design, governance scaffolding, or a safe reorganization plan. Also activate when a repository contains prompts, AI conversations, research, Word documents, spreadsheets, PDFs, images, or mixed knowledge assets rather than a conventional application. This is the authoritative workflow for understanding and organizing an existing repository; use it instead of application-template advice, skill cataloging, or new-repository creation workflows.
OKHP3/skillz · ★ 3 · Data & Documents · score 72

Install: claude install-skill OKHP3/skillz

# okhp3-repository-organizer **OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3) Profile an existing local Git repository before changing it. Use the evidence in its files, history, and available local viewers to explain what the repository is for, what kind of repository it is, what is missing, and which structure would make it easier to understand and maintain. Keep the target pattern content-first and proportional to the repository rather than forcing an application template. --- ## Scope | In scope | Out of scope | |---|---| | Mixed content repositories containing prompts, notes, research, office files, PDFs, images, or configuration | Replacing a content repository with an invented runtime, package, or deployment architecture | | Read-only inventory, purpose discovery, classification, naming and folder proposals | Blind bulk renames, deletion, overwrite, deduplication, or history rewriting | | Selective governance scaffolding and approval-gated Git moves | GitHub pushes, settings changes, issue creation, or publication unless separately authorized | --- ## Inputs and preconditions Required input is a local repository path, plus the user's authorization level: assess, propose, or execute an already approved move set. Treat an absent or inaccessible path, a non-Git folder, a dirty working tree, missing viewers, and unavailable Git or Python as reportable conditions, not reasons to guess. The workflow re