git-workflow

Automate Git branch creation, commits, and pull requests targeting develop.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/kozyszoo/antigravity-handson --skill git-workflow-kozyszoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/kozyszoo/antigravity-handson/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/kozyszoo/antigravity-handson --skill git-workflow-kozyszoo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the repetitive steps of creating branches, committing code with proper formatting, and generating pull requests, significantly speeding up your development cycle.

Core Features & Use Cases

  • Full Workflow Automation: Execute commit, push, and PR creation in one go.
  • Conventional Commits: Enforces standardized commit messages for better project history.
  • Branch Management: Creates feature branches based on established naming conventions.
  • Use Case: After completing a new feature, you can run a single command to create a new branch, commit your changes with a descriptive message, push to the remote, and open a pull request targeting the develop branch.

Quick Start

Use the git-workflow skill to automatically create a new branch named 'feat/add-user-profile'.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I automate creating a branch, committing, and opening a pull request on GitHub?

You can automate this full Git workflow by running a single command to create a feature branch, commit changes with Conventional Commits formatting, push to remote, and open a pull request targeting the develop branch.

How do I enforce Conventional Commits for pull requests and branch creation?

Conventional Commits are enforced automatically during the Git workflow by generating standardized commit messages and creating feature branches using established naming conventions like feature, fix, refactor, docs, and chore.

Can I use this Git workflow automation with feature, fix, and refactor branch types?

Yes, the Git workflow automation supports feature, fix, refactor, docs, chore, perf, test, ci, style, and revert branch types, creating branches and pull requests based on these established naming conventions.

Do I need the gh CLI installed to automate GitHub pull request creation?

Yes, you need the gh CLI installed as a dependency, because the Git workflow automation uses it to push changes to the remote repository and open pull requests targeting the develop branch.

What is the best way to commit code with Co-Authored-By and submit a pull request to develop?

The best way is to use a Git workflow automation that handles commit messages with Co-Authored-By attribution, pushes the branch, and submits the pull request with the develop branch set as the default base.

Why does my pull request target the develop branch instead of main?

Your pull request targets the develop branch because the Git workflow automation strictly uses develop as the base branch for PR submission, enforcing this specific branching strategy for all automated pull requests.