validate-git-hygiene

What problem does it solve?

Inconsistent commit messages, non-standard branch names, and accidental commitment of sensitive files lead to messy repositories, difficult audits, and potential security risks. This Skill automates checks to maintain high git hygiene.

Core Features & Use Cases

• Commit Message Validation: Checks commit messages against Conventional Commits format (e.g., feat: add new feature).
• Branch Naming Compliance: Validates branch names against standard patterns (e.g., feat/*, fix/*, chore/*).
• Sensitive File Detection: Scans for and warns about sensitive files (.env, credentials, .pem) in both tracked and untracked areas.
• Use Case: Integrate this Skill into your pre-commit hooks or CI/CD pipeline to automatically enforce git best practices and prevent security vulnerabilities.

Quick Start

Run git hygiene validation on the current repository

The skill will execute checks and output structured JSON:

{

"status": "warning",

"gitHygiene": {

"branch": {"valid": false},

"commits": {"invalid": 3},

"sensitiveFiles": {"count": 1}

},

"canProceed": false,

"details": "Sensitive files detected - must be removed or added to .gitignore"

}