git-workflow

Generate conventional commit messages and pull request descriptions for Git operations.

4|1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/wyattowalsh/agents --skill git-workflow-wyattowalsh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/wyattowalsh/agents/tree/main/skills/git-workflow
Command: npx skills add https://github.com/wyattowalsh/agents --skill git-workflow-wyattowalsh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commit-parser.py, diff-summarizer.py, and includes scripts (resource) and references (resource) and data (resource) and evals (resource) components.

What problem does it solve?

This Skill streamlines common Git operations, ensuring consistency, clarity, and efficiency in your version control practices, from commit messages to branch strategies.

Core Features & Use Cases

  • Conventional Commits: Generate well-formatted commit messages automatically.
  • PR Descriptions: Create clear and concise pull request summaries.
  • Branch Strategy Guidance: Get recommendations for optimal branching models.
  • Conflict Resolution: Receive step-by-step assistance for merge conflicts.
  • Code Archaeology: Investigate the history and evolution of specific code sections.
  • Bisect Assistance: Efficiently pinpoint regressions using Git's bisect command.
  • Use Case: Before pushing a new feature, use this Skill to generate a conventional commit message and a detailed PR description, ensuring your team's workflow adheres to best practices.

Quick Start

Use the git-workflow skill to generate a conventional commit message for your staged changes.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I generate conventional commit messages for staged changes?

To generate conventional commit messages, you can use this Skill to parse staged diffs and automatically format them according to the Conventional Commits 1.0 standard. It leverages diff summarization and commit parsing scripts to ensure your commit messages adhere to established version control practices.

What is the best way to write clear PR descriptions from recent commits?

The best way to write clear PR descriptions is to use this Skill to summarize your diffs and parse commit history into a concise pull request summary. It automatically processes your recent changes to create a structured overview for your team's workflow.

How do I resolve merge conflicts when pulling changes from another branch?

To resolve merge conflicts, this Skill provides step-by-step guidance tailored to your specific conflicting diffs. It walks you through the resolution process to ensure your branch integrates cleanly without overwriting unintended changes.

Can I use git bisect to pinpoint regressions if I don't know where the bug originated?

Yes, you can use git bisect to pinpoint regressions with this Skill's debugging assistance. It guides you through the bisect process, helping you efficiently narrow down the specific commit that introduced the regression in your codebase.

Does this Skill recommend branching strategies for different team workflows?

Yes, this Skill recommends optimal branching strategies based on your version control needs. It provides guidance on branching models to help your team maintain a clear and efficient workflow across different feature developments and releases.

How do I perform code archaeology to investigate the history of a specific code section?

To perform code archaeology, this Skill investigates the history and evolution of specific code sections by analyzing commit logs and diffs. It helps you understand how and why particular lines of code changed over time.