skills.rest
mfmezger
mfmezgerCOMMUNITY
Explore all skills by this author →
Website𝕏@mfmezgerGitHub

github

Create branches, commit with Conventional Commits, and open GitHub pull requests via gh CLI.

5|Updated Feb 2, 2026
Search Tags:#git#code review#pull request#conventional commits#github#branching
One-click install
npx skills add https://github.com/mfmezger/ai_agent_dotfiles --skill github-mfmezger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/mfmezger/ai_agent_dotfiles/tree/main/shared/skills/github
Command: npx skills add https://github.com/mfmezger/ai_agent_dotfiles --skill github-mfmezger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the entire process of taking local code changes from staging to a deployed GitHub Pull Request, ensuring consistency and adherence to best practices.

Core Features & Use Cases

  • Automated Branching: Creates feature or fix branches following a defined naming convention.
  • Guided Committing: Enforces Conventional Commits format for clear and structured commit messages.
  • Effortless Pushing & PR Creation: Pushes branches and creates pull requests using the GitHub CLI.
  • Use Case: After completing a new feature, use this Skill to automatically create a feat/new-user-authentication branch, stage your changes, commit them with a message like feat(auth): implement user login endpoint, push the branch, and open a pull request for review.

Quick Start

Use the github skill to create a new branch, commit changes, and open a pull request.

Frequently Asked Questions about github

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

FAQPage Schema
How do I automate opening a GitHub pull request from local code changes?▼

Automating a GitHub pull request from local changes requires streamlining your Git workflow by creating a feature branch, staging files, committing with Conventional Commits, and pushing to remote via the GitHub CLI.

What is the best way to enforce Conventional Commits format in a Git workflow?▼

Enforcing Conventional Commits in a Git workflow involves guiding commit message creation to use structured prefixes like feat or fix, ensuring clear history and structured version control for software development tasks.

Do I need the GitHub CLI installed to automate branch creation and PRs?▼

Yes, you need both the Git and GitHub CLI installed and authenticated to automate branch creation, push branches to remote, and open pull requests for code review.

How does automated branch naming work for feature and fix branches?▼

Automated branch naming follows a defined convention based on your task, creating branches like feat/new-user-authentication or fix/login-bug to maintain structured version control.

Can I push changes and create a pull request in one step?▼

Yes, you can push local branches and create a pull request in one automated step using the GitHub CLI, streamlining the end-to-end Git workflow from staging to code review.

When should I use an automated Git workflow for pull requests?▼

You should use an automated Git workflow for pull requests when completing software development tasks requiring structured version control and consistent code review processes across your team.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

rebase-latest-main

Rebase a local git branch onto the latest remote main.

Community
Intermediate
JacobPEvansJacobPEvans
3

rebase-pr

Rebase pull requests onto main with signed commits and GitHub API checks.

Community
Advanced
rlagycksrlagycks
3

springboot-verification

Automate Spring Boot project verification with builds, static analysis, tests, and security scans.

Community
Intermediate
KikolatorKikolator

commit-push-pr

Automate Git staging, commit, push, and pull-request creation.

Community
Intermediate