okhp3-askjamie-repo-organizer
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.
Target: Learning & research. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- okhp3-askjamie-repo-organizer
- Brand-specific overlay
- Scope
- Inputs and preconditions
- Operating contract
- Tool routing
- Workflow
- 1. Inventory the repository
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. -- Before profiling or reorganizing, read references/brand-overlay.md. It tunes repository language and decisions for the AskJamie helpdesk while preserving generic evidence, safety, and approval rules. | 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 publicat
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- docs/archive/skill-redundancy-2026-09-19/brands/askjamie/okhp3-askjamie-repo-organizer/SKILL.md
- Fixed revision
- 7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:54.782Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.