skills.rest
Khamel83
Khamel83COMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Automate git branching, conventional commits, and PR preparation.

Updated Nov 22, 2025
Search Tags:#git#branching#code-quality#git-workflow#pull-request#version-control#conventional-commits
One-click install
npx skills add https://github.com/Khamel83/oneshot --skill git-workflow-khamel83
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Khamel83/oneshot/tree/main/archive/v9/skills/git-workflow
Command: npx skills add https://github.com/Khamel83/oneshot --skill git-workflow-khamel83

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps git histories clean and predictable by guiding branches, commits, and PR preparation using conventional commits, reducing merge conflicts and review overhead.

Core Features & Use Cases

  • Branch naming & management: Enforces consistent prefixes (feature/, fix/, chore/) and helps organize work across teams.
  • Commit messaging: Enforces conventional commit types and formats for structured, searchable history.
  • PR preparation: Generates PR descriptions aligned with the commit history and project guidelines.

Quick Start

Prepare my next commits and PRs using conventional commits.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce conventional commits for git branching and pull requests?▼

Enforce conventional commits for git branching by applying structured prefixes like feature/ and fix/ to branch names, generating clean, PR-ready histories and structured commit messages.

What is the best way to automate pull request preparation from git commit history?▼

Automate pull request preparation by generating PR descriptions aligned with your conventional commit history and project guidelines, reducing merge conflicts and minimizing code review overhead.

Can I use conventional commit messaging to organize feature branches across a team?▼

Use conventional commit messaging to organize feature branches across teams by enforcing consistent prefixes like chore/, ensuring a structured, searchable project history and predictable collaboration.

Does git workflow management help reduce merge conflicts in collaborative projects?▼

Git workflow management reduces merge conflicts in collaborative projects by guiding branch naming and enforcing conventional commit types, keeping git histories clean and predictable.

How do I generate a clean, PR-ready git history using conventional commits?▼

Generate a clean, PR-ready git history by applying conventional commit formats to everyday operations, ensuring structured commit messaging and organized branch management.

What are the limitations of automating git workflow with conventional commits?▼

Automating git workflows with conventional commits requires strict adherence to commit type formats and branch naming prefixes, limiting flexibility for teams not following structured version control guidelines.

Related Skills

Explore More Software Engineering Skills→
mir-ammir-am
1

git-push

Push local git commits and update associated pull requests and changelog entries.

Community
Intermediate
cosmixcosmix
53

ci-cd

Design and automate CI/CD pipelines for GitHub Actions, GitLab CI, and Jenkins.

Community
Advanced
WellApp-aiWellApp-ai
341

code-review

Detect hard-rule violations and quality issues in JavaScript/TypeScript code changes.

Official
Intermediate
paywherebpaywhereb

squash

Squash all branch commits into one via interactive git rebase.

Official
Intermediate