Enforce branch naming and commit message conventions for Git repositories.
npx skills add https://github.com/maragudk/skills --skill git-maragudk
Please help me install this Agent Skill. Skill: git Source: https://github.com/maragudk/skills/tree/main/git Command: npx skills add https://github.com/maragudk/skills --skill git-maragudk
This Skill codifies a refined git workflow aligned with the author's preferences, making commits and branch naming more predictable and consistent with best practices.
add-some-feature without prefixes such as feat/ or hotfix/.Use the git skill whenever you need to create a branch and craft a well-formatted, readable commit message.
High-intent search queries and answers about installing and using this skill.
Branch naming should use short, dash-separated phrases like `add-some-feature` without prefixes such as `feat/` or `hotfix/`. This keeps branch names predictable and readable while avoiding unnecessary naming conventions that clutter version control.
Enclose code identifiers in backticks and reference Go types with package and type names. Append issue references at the end using `See #123, #234` or `Fixes #123, fixes #234`. This ensures commits are searchable and clearly linked to related work.
Codify your preferred branch naming and commit message format into a repeatable workflow. Enforce short, dash-separated branch names, descriptive messages with code formatting, and GitHub issue references to make collaboration predictable and reduce integration friction.
Yes. Apply consistent branch naming and commit message conventions during feature development, bug fixes, and collaborative work on shared repositories. The same guidelines ensure clarity whether you're adding functionality or resolving issues.
No. Avoid amending previous commits unless explicitly instructed. After the first branch commit, use simple, direct messages. This prevents rewriting history on shared work and keeps collaboration predictable.
gajjalaashok75-UIStages modified files, commits conventionally, and pushes to remote tracking repository.
ajilantonyEnforce repository-specific contribution guidelines for issues, branches, commits, and pull requests.
omarluqEnforce Conventional Commits v1.0.0 standards for branches, worktrees, and commit messages.
sgcarstrendsGenerate conventional commit messages conforming to commitlint rules.