home / skills / agno-agi / agno / git-workflow

git-workflow skill

safe

/cookbook/02_agents/skills/sample_skills/git-workflow

This skill guides Git workflow for commits, branches, and pull requests, applying best practices to streamline collaboration and code quality.

npx playbooks add skill agno-agi/agno --skill git-workflow

Review the files below or copy the command above to add this skill to your agents.

Files (3)

SKILL.md

2.2 KB

---
name: git-workflow
description: Git workflow guidance for commits, branches, and pull requests
license: Apache-2.0
metadata:
  version: "1.0.0"
  author: agno-team
  tags: ["git", "version-control", "workflow"]
---
# 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
```markdown
## 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
```bash
git checkout main
git pull origin main
git checkout -b feature/TICKET-123-description
```

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

### Updating Branch
```bash
git fetch origin
git rebase origin/main
```

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

Overview

This skill provides practical Git workflow guidance for commits, branches, and pull requests. It codifies conventional commit messages, branch naming, and PR templates to keep history clear and reviews efficient. Use it to standardize team practices and reduce review friction.

How this skill works

The skill inspects commit messages, branch names, and PR titles to ensure they follow a consistent format and recommended types (feat, fix, docs, etc.). It offers templates and examples for commit bodies, branch naming patterns, and a PR description checklist. It also recommends common commands for starting work, committing changes, updating branches, and creating pull requests.

When to use it

When creating a new feature branch or bugfix branch
When composing commit messages for clarity and traceability
Before opening a pull request to ensure title and description match standards
When rebasing or syncing a branch with main
When writing tests or documentation that require specific commit types

Best practices

Use the commit format type(scope): subject and include a body and footer when needed
Name branches with type/ticket-short-description, e.g., feature/TICKET-123-description
Keep commit subjects short (50 characters) and bodies wrapped at ~72 characters
Stage changes interactively (git add -p) to create focused commits
Rebase onto main before creating a pull request to keep history clean

Example use cases

Create a new feature branch: git checkout -b feature/AUTH-123-oauth-login and follow the commit format
Fix a bug with a clear commit: fix(api): handle null response from external service
Prepare a pull request using the PR template: include Summary, Changes, Testing, and Checklist
Update a branch: git fetch origin && git rebase origin/main to incorporate upstream changes
Maintain repo hygiene: use chore/ branches for dependency updates and refactor/ for internal restructures

FAQ

What commit types should I use?

Use standard types like feat, fix, docs, style, refactor, perf, test, and chore to communicate intent clearly.

How should I title a pull request?

Use the same commit message format for the PR title (type(scope): subject) and include a structured description with Summary, Changes, Testing, and a Checklist.