Validate GitHub template repository paths, references, and folder structure.
npx skills add https://github.com/Tirael/cursor-template --skill repo-hygiene
Please help me install this Agent Skill. Skill: repo-hygiene Source: https://github.com/Tirael/cursor-template/tree/main/.cursor/skills/repo-hygiene Command: npx skills add https://github.com/Tirael/cursor-template --skill repo-hygiene
This skill helps maintain repository hygiene for GitHub templates by validating paths, references, and project structure, ensuring a clean, reusable template.
Run the repo-hygiene check to align the repository with the GitHub template structure and remove clutter.
High-intent search queries and answers about installing and using this skill.
To validate a GitHub template repository structure, check that paths align with canonical sources, allowed directories like src/c4 and src/scripts are enforced, and stray files are eliminated. This skill automates those folder convention checks for a clean, reusable template.
Repository hygiene for a GitHub template means enforcing correct folder conventions, validating references, and eliminating duplication. It ensures no stray files exist and that directories like src/diagrams and src/examples maintain a single source of truth for the project.
Checking for dead links and duplicates in a repo structure requires scanning project references against canonical sources. This skill detects inconsistencies and duplication to ensure a single source of truth for template repositories.
Yes, you can enforce folder restrictions like keeping PlantUML files in src/diagrams, C4 diagrams in src/c4, and scripts in src/scripts. This skill validates allowed directories and eliminates stray files to maintain template structure.
You should run a repository structure validation check before publishing a GitHub template, after reorganizing a repo structure, or following documentation cleanup. This ensures no stray files and correct folder conventions before the template is reused.
The best way to sanitize a GitHub template repo after reorganizing folders is to validate paths and references against canonical sources. This skill standardizes folder conventions and removes clutter to prevent drift between the template and published repo.
BaneeishaqueAudit and reorganize project directories into standard structures with Git.
JeremyDev87Generate READMEs, API docs, ADRs, and CHANGELOGs from repository structure.
adriannoesGenerate, validate, and improve PlantUML diagram syntax.
ncaqThe final result is a function of the initial conditions and the decisions made along the way.
