Enforce standardized Git workflows with Conventional Commits and Husky hooks.
npx skills add https://github.com/FelipePepe/TeamHub --skill rule-gitflow
Please help me install this Agent Skill. Skill: rule-gitflow Source: https://github.com/FelipePepe/TeamHub/tree/main/.agents/skills/rule-gitflow Command: npx skills add https://github.com/FelipePepe/TeamHub --skill rule-gitflow
This skill standardizes Git workflows, enforcing consistent commit messages, branch naming, and release processes to reduce confusion and errors across teams.
Follow the rules when starting work on a new task, ensure you are on the correct branch, perform pre-commit checks, and open a PR once local checks pass.
High-intent search queries and answers about installing and using this skill.
A Git workflow skill enforces consistent commit messages, branch naming, and release processes to reduce confusion and errors across teams by applying rules for branches, merges, releases, and hotfixes.
Managing Git releases and hotfixes requires a branching strategy that separates main and develop branches, guiding PR creation, merge hygiene, and release workflows to ensure a fully traceable project history.
Yes, you can use Husky pre-commit hooks to standardize Git operations by running mandatory checks before commits are applied, ensuring branch naming and commit conventions are satisfied across all branches and merges.
You need to follow a defined branching model using main, develop, feature, and bugfix branches to start standardizing your Git workflow, ensuring you are on the correct branch and passing local checks before opening a PR.
Inconsistent Git commit history causes confusion because it lacks traceable rules for branch naming, pre-commit checks, and PR processes, making it difficult to track feature releases, hotfixes, and merge operations across the team.
compartmentdevAutomates git commits compliant with commitlint type/scope and Husky validation.
sgcarstrendsAutomate software release workflows with semantic-release and conventional commits.
eysenfalkEnforce Git branch naming, commit message formats, and merge policies.
AndreaCadonnaEnforce standardized Git branching, commit, and merge conventions across teams.
