agno-agi

git-workflow

@agno-agi/git-workflow
agno-agi
36,984
4900 forks
Updated 1/18/2026
View on GitHub

Git workflow guidance for commits, branches, and pull requests

Installation

$skills install @agno-agi/git-workflow
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Repositoryagno-agi/agno
Pathcookbook/03_agents/skills/sample_skills/git-workflow/SKILL.md
Branchmain
Scoped Name@agno-agi/git-workflow

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

skills list

Skill Instructions


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

## 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