repo-hygiene

Generate .gitignore templates and pre-commit hooks to block junk and sensitive files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/asmortongpt/Fleet-AzureDevOps --skill repo-hygiene-asmortongpt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-hygiene
Source: https://github.com/asmortongpt/Fleet-AzureDevOps/tree/main/.claude/skills/repo-hygiene
Command: npx skills add https://github.com/asmortongpt/Fleet-AzureDevOps --skill repo-hygiene-asmortongpt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Keeps codebases clean by preventing junk files, AI-generated content, and sensitive data from being committed, enabling safer and more maintainable repos.

Core Features & Use Cases

  • .gitignore templates: Automatically generate comprehensive ignore files for multiple project types.
  • Pre-commit hooks: Block commits containing secrets or unwanted artifacts and run automated checks.
  • Repo audits: Scan for large files, Claude/AI outputs, and tracked sensitive data, plus remediation guidance.
  • Use Case: When initializing a new project, run this skill to generate a robust hygiene baseline and keep history clean.

Quick Start

Create a new repository, initialize hygiene by running the provided scripts and hooks to prevent junk commits from day one.

Frequently Asked Questions about repo-hygiene

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

FAQPage Schema
How do I prevent secrets and sensitive files from being committed to my repository?▼

Pre-commit hooks block commits containing secrets or sensitive files by running automated hygiene checks during your CI/CD pipeline, ensuring polluted repositories are stopped before code is committed. It applies safety checks across multiple tech stacks.

What is the best way to automatically generate a .gitignore file for a new project?▼

Generating a .gitignore file automatically applies comprehensive templates tailored for multiple project types during initialization, creating a robust hygiene baseline to keep junk files and AI-generated content out of your history.

How do I scan an existing repository for large files and tracked sensitive data?▼

Repository audits scan for large files, AI outputs, and tracked sensitive data by running provided audit scripts, providing remediation guidance to clean up polluted codebases and maintain repository safety.

Can I use these pre-commit hooks and hygiene scripts with my existing CI/CD pipeline?▼

Yes, hygiene rules and pre-commit hooks apply during CI/CD pipelines and project initialization, supporting multiple tech stacks without requiring external dependencies to ensure secure and repeatable hygiene practices.

When should I run a repository cleanup to prevent junk files?▼

Run repository cleanups during project initialization or when existing codebases need audits, preventing AI-generated content and junk files from being committed by applying automated hygiene rules and safety checks.

Do I need to install external dependencies to enforce repository hygiene rules?▼

No, the skill operates with zero dependencies, providing scripts, references, and assets internally to enforce hygiene rules, block sensitive files, and generate .gitignore templates autonomously.