Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
agno-agi avatar

Git Workflow

  • 646 installs
  • 41.6k repo stars
  • Updated August 4, 2026
  • agno-agi/agno

git-workflow is an agno-agi agent skill that enforces consistent Git branching, committing, and pull request patterns for developers who want coding agents to follow team git conventions without manual oversight.

About

git-workflow is a well-known agno-agi/agno skill listed on skills.sh with 570 installs that standardizes how coding agents handle branches, commits, and pull requests. It gives agents repeatable patterns so git operations stay aligned with team expectations instead of ad hoc messages and branch names. Developers reach for git-workflow when onboarding agents onto repositories with established git hygiene or when agent-generated commits and PRs need guardrails. The skill spans everyday development from feature branches through review-ready changes. Its skills.sh rank of 8596 reflects catalog placement among community workflow skills.

  • Enforces standardized Git workflow rules for agents
  • Automates branch naming, commit messages, and PR templates
  • Prevents common mistakes like direct main commits
  • Works across local, CI, and agent-driven environments
  • Includes hard-gate checks before merge

Git Workflow by the numbers

  • 646 all-time installs (skills.sh)
  • Ranked #94 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/agno-agi/agno --skill git-workflow

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs646
repo stars41.6k
Last updatedAugust 4, 2026
Repositoryagno-agi/agno

How do coding agents follow team git conventions?

Let their coding agent follow consistent Git branching, committing, and PR patterns without manual oversight.

Who is it for?

Development teams using agno agents who need automated guardrails on branching, commits, and PR workflows across repositories.

Skip if: Repositories with no shared git conventions or developers who only need a one-off commit message template.

When should I use this skill?

An agent is about to create branches, commit code, or open pull requests and the repository expects standardized git workflow behavior.

What you get

Convention-aligned feature branches, commit messages, and pull request steps produced by the agent during development.

  • standardized branches
  • conventional commits
  • PR-ready git steps

By the numbers

  • 570 installs on skills.sh
  • skills.sh catalog rank 8596

Files

SKILL.mdMarkdownGitHub ↗

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

Related skills

How it compares

Choose git-workflow for ongoing agent git hygiene across a project rather than a single-purpose PR description generator.

FAQ

How popular is the git-workflow skill?

The agno-agi/agno git-workflow skill reports 570 installs on skills.sh with a catalog rank of 8596 and well-known sourceType status.

What does git-workflow standardize?

git-workflow teaches coding agents consistent Git branching, committing, and pull request patterns so repository work follows team conventions without developers micromanaging each git step.

Git & Pull Requestsgitintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.