skills.rest
cheetah-alo
cheetah-aloCOMMUNITY
Explore all skills by this author →
Website𝕏@techieesp_GitHub

commit-hygiene

Enforce repository commit message format and pre-commit safety checks.

Updated May 17, 2026
Search Tags:#git#pull request#security#commit message#code hygiene#pre-commit checklist
One-click install
npx skills add https://github.com/cheetah-alo/NegritaOS --skill commit-hygiene-cheetah-alo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-hygiene
Source: https://github.com/cheetah-alo/NegritaOS/tree/main/.codex/skills/commit-hygiene
Command: npx skills add https://github.com/cheetah-alo/NegritaOS --skill commit-hygiene-cheetah-alo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents messy, risky, or unclear Git commits by enforcing consistent commit messages and protecting against accidental inclusion of secrets or generated artifacts.

Core Features & Use Cases

  • Commit message standards: Enforces the repository format <type>(<scope>): <description> with scoped, rationale-focused descriptions.
  • Change hygiene controls: Promotes one logical change per commit and blocks unrelated refactors from being hidden inside bugfixes or features.
  • Pre-commit safety checklist: Reduces risk of leaking credentials by preventing secret-bearing or temporary/local/generated artifacts from being committed.

Quick Start

Use this skill before you push any change by reviewing your staged diff and ensuring your commit message is scoped, explains the why, and contains no secrets or generated artifacts.

Frequently Asked Questions about commit-hygiene

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

FAQPage Schema
How do I enforce a standard git commit message format for my team?▼

To enforce a standard git commit message format, require repository-compliant `<type>(<scope>): <description>` formatting. This structure ensures scoped, rationale-focused descriptions, improving version control history clarity and traceability for day-to-day engineering.

What is a pre-commit checklist for preventing secrets in git?▼

A pre-commit checklist for preventing secrets in git is a safety control that blocks secret-bearing or temporary generated artifacts from being committed. It reduces the risk of leaking credentials by verifying staged changes before pushing.

How do I keep my git commits scoped to one logical change?▼

To keep git commits scoped to one logical change, apply one-logical-change discipline to separate unrelated refactors from bugfixes or features. This prevents hidden modifications and maintains clean, traceable version control history.

Can I use a pre-commit checklist for pull request commit reviews?▼

Yes, you can use a pre-commit checklist for pull request commit reviews. The checklist enforces repository commit standards by verifying message formatting, one-logical-change discipline, and blocking secrets or generated artifacts during PR commit review workflows.

What is the best way to clean up staged changes before committing?▼

The best way to clean up staged changes before committing is to review your staged diff and ensure your commit contains no secrets or generated artifacts. Apply one-logical-change discipline to keep the commit clean, scoped, and safe.

Related Skills

Explore More Software Engineering Skills→
mkittmkitt
6

commit-groups

Analyze uncommitted Git changes to propose logical commit groupings.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
arcasilesgrouparcasilesgroup
54

commit

Stage, lint, detect secrets, commit, and push code with governance checks.

Official
Advanced
ss49919201ss49919201

git-add-commit

Stage git changes and generate commit messages from diffs.

Community
Basic