Standardize Git commits, branches, and pull requests with Conventional Commits.
npx skills add https://github.com/miptah21/skills --skill git-workflow-miptah21
Please help me install this Agent Skill. Skill: git-workflow Source: https://github.com/miptah21/skills/tree/main/.agents/skills/git-workflow Command: npx skills add https://github.com/miptah21/skills --skill git-workflow-miptah21
It prevents messy commit history, inconsistent branching, and vague pull requests by standardizing how developers structure changes in Git.
<type>(<scope>): <description> format with clear rules for subject length and imperative mood.<type>/<short-description> pattern to make work purposefully searchable.Ask your agent to prepare a commit message, branch name, and PR description following the git-workflow conventions for the changes you are about to submit.
High-intent search queries and answers about installing and using this skill.
Conventional commits require a predictable format using a type, scope, and imperative description. This structure keeps the subject clear and limits length, making the change history readable and reviewable across collaborative repositories.
A pull request description template should include What, Why, How, Testing, and Checklist sections. Providing testing evidence and context within the PR description ensures reviewers understand the changes and verifies safe merge practices.
The best way to name Git branches is using a structured pattern combining the type and a short description, like type/short-description. This deterministic naming convention makes work purposefully searchable for bug fixes, features, or CI maintenance.
A safe merge strategy that avoids force-pushes recommends using squash for feature branches and rebase to keep branches up-to-date. This approach standardizes release preparation and prevents messy commit history during collaborative work.
Yes, this Git workflow standardization applies to documentation updates, feature work, bug fixes, and CI maintenance. It enforces consistent commit, branch, and pull request conventions across any collaborative repository changes.
maveroxAnalyze git diffs to provide structured code review feedback.
mako-aiAutomate build, test, packaging, and release workflows for Mako Desktop and Local Agent.
YoshikemoloGenerate Git branch names and validate commit messages against Jira issues.
Sir-chawakornGenerate changelogs from Git commits in Markdown format.