git-workflow

Automates branch creation, commit, push, and GitHub pull request generation.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/Cohey0727/CodingAgentTools --skill git-workflow-cohey0727
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Cohey0727/CodingAgentTools/tree/main/skills/git-workflow
Command: npx skills add https://github.com/Cohey0727/CodingAgentTools --skill git-workflow-cohey0727

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually running the full Git flow from committing changes to opening a pull request involves many repetitive steps and easy-to-miss mistakes, such as pushing directly to main or forgetting the PR template. This Skill executes the entire branch-to-PR workflow in one shot with built-in safety checks. ## Core Features & Use Cases - End-to-End Automation: Detects generic branches (main, develop, etc.), auto-generates a conventional branch name, commits via the /commit skill, pushes, and creates the PR with gh CLI. - PR Template Awareness: Searches the repository for pull request templates and fills them in, falling back to a default Summary/Changes/Test Plan format. - Safety Guardrails: Blocks pushes to generic branches, never uses force-push, detects existing PRs to avoid duplicates, and supports draft PRs on request. - Use Case: You finish a bug fix on the develop branch and say "create a PR" — the Skill branches off as fix/null-response-handling, commits, pushes, and opens a PR against the detected base branch, returning the URL. ## Quick Start Ask the agent to create a pull request for my current changes using the git-workflow skill.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I create a GitHub pull request automatically from my changes?▼

Invoke the git-workflow skill with your uncommitted changes present. It analyzes the diff, creates a conventional branch like feat/add-user-auth, commits, pushes to origin, and runs gh pr create with a generated title and body, returning the PR URL.

How does the skill generate branch names and PR titles?▼

Branch names follow the format type/short-description using only the types feat, fix, refactor, chore, docs, or test, derived from analyzing git diff output. PR titles use conventional commit format, stay under 70 characters, and are written in English.

Does the skill use the repository's pull request template?▼

Yes, it searches for pull request template files with a glob pattern, preferring .github/pull_request_template.md, and fills each template section. If no template exists, it falls back to a default Summary, Changes, and Test Plan format.

Can I create a draft pull request with this workflow?▼

Yes, request a draft explicitly with a flag like --draft or by saying draft or WIP in your message. The skill then passes the draft option to gh pr create; otherwise it creates a normal pull request by default.

What happens if I run the workflow on the main branch?▼

The skill never pushes directly to generic branches such as main, master, develop, staging, or release. It first creates a new appropriately named branch from your changes, then commits and pushes that branch before opening the PR.

What happens if a pull request already exists for my branch?▼

The skill checks for an existing PR using gh pr view before creating one. If a PR already exists, it notifies you and skips creation, since pushing additional commits automatically updates the existing pull request.