New to Claude Skills? Learn how to install them →

agno-agi on GitHub

Git Workflow

Free

Streamline your Git commits, branches, and pull requests.

by agno-agi41.6k stars on agno-agi/agno
1 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What Git Workflow does

The Git Workflow skill is designed to assist developers in managing their Git operations efficiently by providing structured guidelines for commits, branch naming, and pull requests. By adhering to best practices, this skill helps maintain a clean and organized version control history, which is essential for collaborative software development. It offers a clear format for commit messages, ensuring that each commit is informative and easy to understand, which is crucial for tracking changes over time.

This skill includes a script for generating and validating commit messages based on predefined types such as 'feat', 'fix', and 'chore'. These types help categorize changes effectively, making it easier for team members to comprehend the purpose of each commit. Additionally, the skill provides a standardized naming convention for branches, which aids in identifying the purpose of a branch at a glance. This organization is particularly useful in larger projects where multiple features and fixes are being developed simultaneously.

For pull requests, the skill outlines a comprehensive template to ensure that all necessary information is included. This includes a summary of changes, testing details, and a checklist to confirm that all relevant tasks have been completed. By following these guidelines, developers can create clear and concise pull requests that facilitate smoother code reviews and integration into the main codebase.

Overall, the Git Workflow skill is an invaluable tool for developers looking to enhance their Git practices, improve collaboration, and maintain high code quality throughout the development lifecycle.

When to use it

Use this skill when you need structured guidance for managing Git workflows in a collaborative environment.

When not to use it

This skill may not be suitable for users who prefer a more flexible or informal approach to version control.

What you can build with it

Generating Commit Messages

Use the skill to create well-structured commit messages that follow best practices, improving code clarity.

Organizing Branches

Adopt the branch naming conventions provided to keep your feature and fix branches organized and easy to identify.

Creating Pull Requests

Utilize the pull request template to ensure all necessary information is included, facilitating smoother code reviews.

How to install Git Workflow

View source

1. Install with the skills CLI

npx skills add agno-agi/agno/git-workflow --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by agno-agi

Git Workflow Skill

You are a Git workflow assistant. Help users with commits, branches, and pull requests following best practices.

Commit Message Guidelines

For commit message generation and validation, use get_skill_script("git-workflow", "commit_message.py").

Format

<type>(<scope>): <subject>

<body>

<footer>

Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation only
  • style: Formatting, no code change
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Performance improvement
  • test: Adding or updating tests
  • chore: Maintenance tasks

Examples

feat(auth): add OAuth2 login support

Implemented OAuth2 authentication flow with Google and GitHub providers.
Added token refresh mechanism and session management.

Closes #123
fix(api): handle null response from external service

Added null check before processing response data to prevent
NullPointerException when external service returns empty response.

Fixes #456

Branch Naming

Format

<type>/<ticket-id>-<short-description>

Examples

  • feature/AUTH-123-oauth-login
  • fix/BUG-456-null-pointer
  • chore/TECH-789-update-deps

Pull Request Guidelines

Title

Follow commit message format for the title.

Description Template

## Summary
Brief description of what this PR does.

## Changes
- Change 1
- Change 2

## Testing
How was this tested?

## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No breaking changes

Common Commands

Starting Work

git checkout main
git pull origin main
git checkout -b feature/TICKET-123-description

Committing

git add -p  # Interactive staging
git commit -m "type(scope): description"

Updating Branch

git fetch origin
git rebase origin/main

Creating PR

git push -u origin feature/TICKET-123-description
# Then create PR on GitHub/GitLab

Frequently asked questions about Git Workflow

Similar skills