organize-repository

Validate file placement and manage tracked relocations with git mv.

1|Updated Jul 12, 2026

Search Tags:#git #architecture #maintenance #cleanup #repository #organization

Ready to run

npx skills add https://github.com/Tyler-R-Kendrick/slm-training --skill organize-repository

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: organize-repository
Source: https://github.com/Tyler-R-Kendrick/slm-training/tree/main/.agents/skills/organize-repository
Command: npx skills add https://github.com/Tyler-R-Kendrick/slm-training --skill organize-repository

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents repository sprawl and architectural decay by enforcing strict placement rules for files and directories, ensuring the codebase remains navigable and maintainable as it grows.

Core Features & Use Cases

Canonical Path Enforcement: Ensures all files are placed in their designated directories (e.g., src/ for code, docs/ for documentation).
Relocation Safety: Mandates the use of git mv to preserve history and requires simultaneous updates to imports and links.
Use Case: When adding a new experimental module, this Skill guides you to place it in the correct subdirectory and update the repository policy checker to ensure it meets project standards.

Quick Start

Use the organize-repository skill to validate the placement of the new module and ensure all internal links are correctly updated.

Frequently Asked Questions about organize-repository

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

FAQPage Schema

How do I enforce canonical directory structure and prevent repository sprawl?▼

To prevent repository sprawl, enforce canonical directory structure by validating file placement against defined path policies, ensuring code stays in src/ and documentation in docs/. This maintains navigability and architectural integrity as the codebase grows.

What is the best way to relocate files in a git repository without losing history?▼

The best way to relocate files in a git repository without losing history is to use git mv for tracked relocations. This preserves version history while mandating simultaneous updates to imports and internal links to maintain architectural consistency.

How do I add a new experimental module to a project while maintaining directory organization standards?▼

To add a new experimental module while maintaining directory organization, place the module in the correct designated subdirectory and update the repository policy checker. This ensures the new addition meets project standards and path policies.

Does repository cleanup require git-based version control operations?▼

Yes, repository cleanup requires git-based version control operations to safely manage tracked relocations and preserve history. Adhering to defined path policies during maintenance tasks ensures architectural integrity during directory restructuring and module addition.

When should I restructure project directories and update documentation placement?▼

You should restructure project directories and update documentation placement when architectural decay threatens maintainability. Enforcing strict placement rules for files and directories ensures the codebase remains navigable during maintenance and module addition.

What are the limitations of automated file placement validation for codebase maintenance?▼

Automated file placement validation for codebase maintenance is limited by its reliance on predefined path policies and cannot dynamically interpret undocumented architectural intent. It requires manual updates to imports and links after applying git mv relocations.