okhp3-repository-organizer

Topics in the source

• okhp3-repository-organizer
• Scope
• Inputs and preconditions
• Operating contract
• Tool routing
• Workflow
• 1. Inventory the repository
• 2. Apply the portability gate

OverKill Hill P³ · overkillhill.com · 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. -- | 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 | -- 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 inacc

This is an excerpt. Refer to the complete source and its current requirements.