Enforce Git commit prefixes by directory for consistent messages.
npx skills add https://github.com/crmeb/CRMEB --skill git-crmeb
Please help me install this Agent Skill. Skill: Git提交规范 Source: https://github.com/crmeb/CRMEB/tree/main/.trae/skills/git-commit Command: npx skills add https://github.com/crmeb/CRMEB --skill git-crmeb
This policy standardizes Git commit messages across a project by enforcing directory-based prefixes on every commit, improving traceability, reviews, and changelog generation.
Prefix every commit message with the appropriate directory tag to enforce consistency.
High-intent search queries and answers about installing and using this skill.
To standardize Git commit messages, you enforce directory-based prefixes on every commit, ensuring messages reflect impacted areas like crmeb/ or docker-compose/ to improve history readability and code reviews.
Directory-based prefixes for Git commit conventions provide predictable commit semantics, improving traceability, code reviews, and changelog generation across multi-directory project workflows.
The correct Git commit message structure requires prefixing the message with the relevant directory tag, such as crmeb/ or template/, to clearly indicate scope and codify required formats for team collaboration.
Yes, you can apply this Git commit convention to dev-docs and docker-compose workflows, as it specifically targets these directories to enforce consistent prefix formats and guide teams during commits.
The best way to enforce consistent Git commit prefixes is to codify required prefix formats and example patterns, guiding team members to prefix every commit with the appropriate directory tag for consistency.
Tx1207Create a new project from a template, initialize uv, and configure a local Git repository.
plurigridGenerate user-facing changelogs from git commit history.
lukevellaEnforce emoji-prefixed commit messages in Git workflows.
olga-mirGenerate commit messages conforming to the Conventional Commits specification.
