skills.rest
Conradmaker
ConradmakerCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Automate Git workflows from branch strategy to PR creation with GitHub CLI.

Updated Apr 27, 2026
Search Tags:#git#workflow#github#branching#pull-request#gh-cli#commit-conventions
One-click install
npx skills add https://github.com/Conradmaker/copilot-cockpit --skill git-workflow-conradmaker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Conradmaker/copilot-cockpit/tree/main/.github/skills/git-workflow
Command: npx skills add https://github.com/Conradmaker/copilot-cockpit --skill git-workflow-conradmaker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflows often suffer from ambiguity in branching, committing, and PR processes, causing delays and integration issues. This Skill provides a unified guide that combines GitHub Flow with Conventional Commits to align team practices and reduce decision fatigue.

Core Features & Use Cases

  • Branch strategy guidance: main, feature/, fix/, docs/, refactor/
  • Commit conventions based on Conventional Commits with gh CLI integration
  • PR creation, review, and automation guidance using gh pr commands
  • Clear guidance for naming, reviews, and automation references to the workflow

Quick Start

Create a feature branch from main and open a draft PR using gh pr while following the recommended branch naming and commit conventions.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I standardize Git workflows for feature, fix, and refactor tasks?▼

Standardize Git workflows by combining GitHub Flow with Conventional Commits to enforce branch naming conventions, commit message guidelines, and automated PR creation using the GitHub CLI.

What is the best way to automate pull request creation with GitHub Flow?▼

Automate pull request creation using GitHub CLI commands, opening draft PRs directly from feature branches while adhering to strict branch naming and commit conventions to align team practices.

Does this Git workflow approach support teams using Conventional Commits?▼

Yes, this approach fully supports Conventional Commits by enforcing commit message guidelines across feature, fix, docs, and refactor tasks to reduce ambiguity and decision fatigue for engineering teams.

How do I structure branch names for GitHub Flow across different task types?▼

Structure branch names using specific prefixes like feature/*, fix/*, docs/*, and refactor/* branching directly from main to maintain clear guidance for reviews and integration.

Why use the GitHub CLI for PR workflows instead of manual creation?▼

Using the GitHub CLI for PR workflows enforces consistent automation, standardizes pull request creation and review processes, and reduces integration issues caused by manual branch and commit ambiguity.

Related Skills

Explore More Software Engineering Skills→
Nabilhassan12345Nabilhassan12345

pr-submit

Create a GitHub pull request from the active branch with guided prompts.

Community
Intermediate
dmzoneilldmzoneill
2

review-pr

Automate Git merge request reviews across GitLab with commit, pipeline, and Jira checks.

Community
Advanced
GolferGeekGolferGeek

GitHub Workflow

Standardize GitHub branching, pull requests, code reviews, and CI/CD pipelines.

Community
Basic
h4vzzh4vzz
33

version-control

Manage Git repositories and collaborative workflows across GitHub, GitLab, and Bitbucket.

Community
Advanced