Standardize Git commit messages, branch names, and history workflows.
npx skills add https://github.com/Muvon/octomind-tap --skill git-workflow-muvon
Please help me install this Agent Skill. Skill: git-workflow Source: https://github.com/Muvon/octomind-tap/tree/main/skills/git-workflow Command: npx skills add https://github.com/Muvon/octomind-tap --skill git-workflow-muvon
Git workflows often lead to messy histories, inconsistent commit messages, and confusing branch names that make reviews and releases harder.
Use case: You are preparing a pull request and want teammates to be able to quickly understand what changed, why it changed, and how it should be released—without manually policing conventions.
Activate the git-workflow skill to format your next commit message, name your feature branch, and apply a rebase/squash workflow before opening a PR.
High-intent search queries and answers about installing and using this skill.
Conventional commits format requires a type/scope/summary structure with wrap rules and optional footers like Fixes or Closes. This produces consistent commit messages that improve changelogs and make review scanning easier before opening a PR.
Git branch naming should follow a type-based, kebab-case pattern. This convention keeps branches organized by purpose, making it easier to track feature work and collaborate across any git-based project team workflow.
A rebase workflow keeps git history linear by avoiding direct commits to main and rebasing feature branches instead of merging. It enforces atomic changes and squashes WIP commits before PRs to maintain a clean, reviewable repository history.
Semantic version tags are needed when tagging releases in a git workflow that uses conventional commits. They provide structured version tracking that aligns with commit message types, ensuring clear release boundaries for team collaboration.
Git workflow rules apply across any git-based project and team workflow. There are no specific dependencies or components required, allowing you to enforce commit conventions, branch naming, and rebase practices in your existing repositories.
MayaDispelerEnforce git commit message formats, branch naming, and pull request guidelines.
voidrotGenerate changelogs and release notes from commit history and tags.
YoshikemoloGenerate Git branch names and validate commit messages against Jira issues.
ilonatommyConsolidate multiple Git commits into a single commit using rebase, reset, or merge strategies.
