Git Workflow

This is a structured guide for standardizing your team's Git practices. It gives you conventional commit formats (feat, fix, docs, etc.), branch naming patterns like feature/TICKET-123-description, and a PR template with checklist items. There's a Python script for commit message validation, though the real value is having all these conventions in one place so you stop debating formats in code reviews. It's opinionated in a good way, basically Conventional Commits with ticket IDs baked in. If your team already has standards, you won't need this. If you don't, it's a reasonable starting point that covers the workflow basics without getting religious about rebase versus merge.

skills.sh installs: 669
GitHub stars: 43.1K
last updated: Aug 21, 2026

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

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