What problem does it solve? Repositories that grew organically from folders of notes, prompts, Word documents, PDFs, and research files often lack clear purpose, safe naming, and governance structure. This Skill inspects the evidence before changing anything, explains what the repository is for, and produces a safe, reversible reorganization plan instead of forcing an application template onto mixed content. ## Core Features & Use Cases - Evidence-based profiling: Runs a read-only inventory script and separates confirmed, inferred, and unknown claims to assign a repository archetype with confidence levels. - Cross-platform naming gate: Applies an ASCII lowercase hyphen naming profile and detects Windows-reserved names, case-folded and Unicode-normalized collisions, and path-length violations before any rename. - Approval-gated migration: Proposes a current-path to proposed-path mapping table, executes only approved moves with git mv, and verifies links, diffs, and portability diagnostics afterward. - Use Case: You have a local Git repository full of Markdown notes, paired DOCX/PDF exports with version suffixes, and filenames with spaces and Unicode. Use this Skill to profile the repository, design a topic-based structure, and execute a verified migration plan that survives Windows, macOS, Linux, GitHub URLs, and different shells. ## Quick Start Scan this local Git repository, determine what it is for, check its filenames for cross-platform portability, and prepare an approval-gated reorganization plan without changing any files yet.
