Guide Git workflows for commits, branches, and pull requests.
npx skills add https://github.com/drdanmaggs/rocket-fuel --skill git-workflow-drdanmaggs
Please help me install this Agent Skill. Skill: git-workflow Source: https://github.com/drdanmaggs/rocket-fuel/tree/main/internal/plugin/skills/git-workflow Command: npx skills add https://github.com/drdanmaggs/rocket-fuel --skill git-workflow-drdanmaggs
Git teams often struggle with inconsistent commit messages, unclear branching strategies, and PR processes that slow down delivery. This Skill provides a structured, best-practice guide to standardize those workflows and reduce review cycles.
Initiate a request to review your last commit message and propose improvements.
High-intent search queries and answers about installing and using this skill.
To standardize Git commit messages across multiple repositories, adopt conventional commit guidelines with type, scope, and description. This workflow enforces consistent commit structures, reducing review cycles and making release tracking predictable across teams.
The best way to structure branch naming conventions is using stable naming patterns that reflect the work type and ticket IDs. This Git workflow provides clear branch naming rules to organize development efforts and make tracking contributions straightforward.
To create pull request templates that speed up reviews, apply structured guidelines for PR titles, descriptions, and checklists. This workflow standardizes PR content to ensure reviewers receive complete context, reducing back-and-forth cycles.
Yes, you can use conventional commits to enforce Git workflow standards for new contributors. This workflow guides onboarding by providing structured rules for commits, branches, and pull requests, ensuring immediate adherence to best practices.
Guided Git workflow handles PR standardization by enforcing pull request title, description, and checklist templates. Teams apply the same workflow rules across multiple repositories to standardize releases and ensure consistent review processes.
No, you do not need existing Git scripts to enforce branching and commit standards. This workflow includes optional scripts and references to support deterministic tasks, providing the necessary templates and guidelines out of the box.
mcj-coderConfigure Git branching strategies, Conventional Commits, and merge rules.
1Mangesh1Generate changelogs and release notes from Git history using conventional commits.
netresearchStandardize Git branching, commit conventions, and PR workflows across teams.
LarryHsiaoGenerate conventional commit messages from git diffs and commit after approval.
