repo-hygiene

Validate GitHub template repository paths, references, and folder structure.

Updated Feb 4, 2026

Search Tags:#template #github #validation #structure #deduplication #hygiene #repo

Ready to run

npx skills add https://github.com/Tirael/cursor-template --skill repo-hygiene

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintain repository hygiene for GitHub templates by validating paths, references, and project structure, ensuring a clean, reusable template.

Core Features & Use Cases

Enforces canonical paths and references to prevent drift between template and published repo.
Validates allowed directories (C4 diagrams in src/c4/, PlantUML in src/diagrams/, scripts in src/scripts/, examples in src/examples/) and eliminates stray files.
Detects duplicates and inconsistencies to ensure a single source of truth for the template repository.
Use Case: before publishing a GitHub template or after reorganizing repo structure, run this skill to sanitize and standardize the template.

Quick Start

Run the repo-hygiene check to align the repository with the GitHub template structure and remove clutter.

Frequently Asked Questions about repo-hygiene

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

FAQPage Schema

How do I validate my GitHub template repository structure before publishing?▼

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.

What is repository hygiene for a GitHub 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.

How do I check for dead links and duplicates in my repo structure?▼

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.

Can I enforce specific folder restrictions like keeping PlantUML files in src/diagrams?▼

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.

When should I run a repository structure validation check?▼

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.

What's the best way to sanitize a GitHub template repo after reorganizing folders?▼

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.