How do I indicate a breaking change using this skill?

You can signal a breaking change by adding an exclamation mark (!) immediately before the colon in your commit message, such as feat(api)!: change endpoint structure.

Does this skill allow Co-Authored-By trailers?

No, the Engram project standards specifically prohibit the use of Co-Authored-By trailers in commit messages.

What are the allowed commit types?

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

Why was my branch name rejected by the ruleset?

Branches must follow the type/description pattern (e.g., feat/new-feature) and use only lowercase letters, numbers, dots, underscores, or hyphens.

What commit message format does this skill enforce?

It enforces the Conventional Commits specification using the format ( ): , where the type must be one of the allowed lowercase values like feat, fix, or docs.

Engram Commit Hygiene

Name: Engram Commit Hygiene
Author: Gentleman-Programming

byGentleman-Programming

•

1,850

•

开发者工具

Enforces Conventional Commits and standardized branch naming conventions to maintain a clean, machine-readable repository history.

The Engram Commit Hygiene skill ensures that every contribution to the Engram project adheres to strict version control standards enforced by GitHub rulesets. By guiding users through Conventional Commits and specific branch naming patterns, it prevents rejected pushes and streamlines the code review process. This skill is essential for developers who need to maintain logical commit histories, document breaking changes correctly, and follow project-specific best practices such as avoiding generated files and specific metadata trailers.

主要功能

01Real-time guidance on selecting appropriate commit types like feat, fix, and chore

02Standardization of branch naming using the mandatory type/description format

03Automated pre-commit checklists to ensure diff quality and security

041,850 GitHub stars

05Support for breaking change indicators and optional scoping in messages

06Validation of Conventional Commit messages against strict regex patterns

使用场景

01Reviewing local staged changes for accidental inclusion of secrets or generated files

02Creating new development branches that satisfy remote repository rulesets

03Drafting compliant commit messages that explain the 'why' behind code changes

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