git-workflow

Provide Git workflow guidance for commits, branches, and pull requests.

32|5|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/akaszubski/autonomous-dev --skill git-workflow-akaszubski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/akaszubski/autonomous-dev/tree/main/plugins/autonomous-dev/skills/git-workflow
Command: npx skills add https://github.com/akaszubski/autonomous-dev --skill git-workflow-akaszubski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent Git practices lead to messy histories, difficult code reviews, and merge conflicts, slowing down development and increasing frustration. This skill provides clear guidelines for commit messages, branching strategies, and pull request workflows, ensuring a smooth and efficient development process.

Core Features & Use Cases

  • Commit Conventions: Standardized format for clear, descriptive commit messages (e.g., feat:, fix:, docs:).
  • Branching Strategies: Guidance on effective feature branch workflows, including rebasing, merging, and maintaining protected main branches.
  • Pull Request Guidelines: Best practices for PR titles, descriptions, size, and a structured code review process.
  • Use Case: When onboarding a new team member, use this skill to quickly bring them up to speed on your project's Git standards, ensuring all contributions are consistent and easy to review.
  • Use Case: Automatically generate a CHANGELOG.md from conventional commit messages, saving time on release preparation.

Quick Start

This is a knowledge skill, auto-activated by relevant keywords.

To get guidance on Git, simply ask:

"What are the best practices for writing Git commit messages?" "How should I structure my pull request description?"

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I write commit messages that follow conventions?

Conventional commits use a standardized format with a type prefix (feat:, fix:, docs:, etc.) followed by a description. This format makes commit histories readable, enables automated changelog generation, and clarifies the nature of each change at a glance.

What's the best way to structure a pull request for code review?

A well-structured pull request includes a clear title, detailed description of changes and rationale, a reasonable scope, and links to related issues. This practice streamlines code review, reduces merge conflicts, and maintains project history clarity.

How should I organize branches in a collaborative Git workflow?

Use a branch naming strategy tied to work type (feature/, bugfix/, release/) and naming conventions. Maintain a protected main branch, use feature branches for development, and rebase or merge consistently to keep history clean and prevent conflicts.

Can I automatically generate a changelog from my commit history?

Yes—conventional commits enable automated changelog generation tools to parse commit types and extract release notes. This eliminates manual changelog maintenance and ensures release documentation stays synchronized with actual code changes.

What should I do when onboarding a new team member to our Git practices?

Use documented Git standards covering commit conventions, branching strategies, and PR workflows as an onboarding reference. This ensures consistent contributions immediately and reduces friction when new members integrate into the collaborative development process.