Why are branch names restricted to lowercase?

Standardizing on lowercase for branch names prevents case-sensitivity issues across different operating systems and keeps the repository visual history clean.

What types are allowed in commit messages?

Allowed types include feat, fix, docs, refactor, chore, style, perf, test, build, ci, and revert.

Does it support breaking changes?

Yes, it supports the Conventional Commits standard of adding an exclamation mark (!) before the colon to signal a breaking change.

What are Conventional Commits?

Conventional Commits is a lightweight convention for commit messages that provides a set of rules for creating an explicit commit history, making it easier to write automated tools on top of.

How does this skill help with GitHub rulesets?

This skill provides the exact regex and formatting rules used by the Engram repository's GitHub rulesets, allowing Claude to validate your work before you push and face a rejection.

Engram Commit Hygiene

Name: Engram Commit Hygiene
Author: Gentleman-Programming

byGentleman-Programming

•

1,850

•

Developer Tools

Enforces standardized Conventional Commits and branch naming patterns to maintain a professional and automated repository history.

The Engram Commit Hygiene skill provides Claude with the specific rules and regex patterns required to contribute to the Engram ecosystem. By enforcing the Conventional Commits specification and a strict 'type/description' branch naming convention, this skill ensures that all contributions are machine-readable and human-friendly. It helps developers avoid common pitfalls like improper casing, invalid types, or accidental inclusion of local artifacts, effectively preventing push rejections from GitHub rulesets while streamlining the PR review process.

Key Features

011,850 GitHub stars

02Strict Conventional Commits validation using regex patterns

03Pre-commit safety checklist to prevent leaking secrets or binaries

04Identification and marking of breaking changes using standard syntax

05Categorization of changes into types like feat, fix, and refactor

06Standardized branch naming enforcement (type/description)

Use Cases

01Drafting compliant commit messages that pass automated GitHub ruleset checks

02Creating and naming development branches that align with project standards

03Reviewing existing PR commit histories for consistency and clarity

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add gentleman-programming/engram commit-hygiene

For use in Claude.ai and ChatGPT

Download Skill