git-workflow

Automate Git and GitHub workflows for PRs, branches, and CI checks.

1|1|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/BumpyClock/dotfiles --skill git-workflow-bumpyclock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/BumpyClock/dotfiles/tree/main/.ai_agents/skills/git-workflow
Command: npx skills add https://github.com/BumpyClock/dotfiles --skill git-workflow-bumpyclock

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

Git workflows are frequently error-prone and tedious to manage manually across feature work, reviews, and CI pipelines. This skill provides a structured, automated approach to coordinating PRs, commits, branches, and checks using Conventional Commits and GitHub Flow to improve consistency and velocity.

Core Features & Use Cases

  • PR creation & review automation: generate, describe, and track PRs with standard messages and checks.
  • Branch lifecycle management: create, name, switch, and clean up feature/release branches according to the defined prefixes.
  • Conventional commits & CI integration: enforce commit styles and ensure CI checks are wired into PR workflows.

Quick Start

Create a feature branch named feature/your-feature, open a PR with a conventional commit message, and ensure CI checks pass.

Frequently Asked Questions about git-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request creation and code reviews using GitHub Flow?

Automating pull request creation and code reviews using GitHub Flow requires coordinating branch management, conventional commits, and CI checks. This skill structures that end-to-end workflow via the gh CLI to generate, describe, and track PRs automatically.

What is the best way to enforce conventional commits across feature branches and CI pipelines?

Enforcing conventional commits across feature branches and CI pipelines is handled by automating branch lifecycle management and wiring commit style checks into PR workflows. This ensures consistent commit messages and automated CI validation before merging.

Do I need the GitHub CLI installed to automate branch management and changelog updates?

Yes, you need the GitHub CLI (gh) installed and authenticated. This skill depends on the gh CLI to execute automated tasks, manage branch lifecycles, coordinate merging strategies, and update changelogs across your repositories.

Can I use this workflow automation for managing multiple feature branches and release prefixes?

Yes, this workflow automation supports managing multiple feature and release branches. It creates, names, switches, and cleans up branches according to your defined prefixes while coordinating PRs and CI checks across teams and repositories.

Why does manual git workflow coordination become error-prone for teams?

Manual git workflow coordination becomes error-prone due to the tedious management of feature work, code reviews, and CI pipelines across repositories. Automating these steps with structured GitHub Flow and conventional commits improves consistency and velocity.

What are the limitations of automating git workflows with the gh CLI?

Automating git workflows with the gh CLI is limited to GitHub-hosted repositories and depends on local CLI authentication. It does not manage infrastructure deployment and requires predefined branch prefixes to execute automated task steps correctly.