Git Workflow · Agno

Git workflow guidance for commits, branches, and pull requests following best practices, including commit message format and types, branch naming conventions, a pull request description template, and common Git commands.

Tasks

Write commit messages in the conventional format <type>(<scope>): <subject> with body and footer
Create branches named <type>/<ticket-id>-<short-description> (e.g., feature/AUTH-123-oauth-login)
Draft pull request titles and descriptions using the provided template (Summary, Changes, Testing, Checklist)
Start work from an updated main branch and create a feature branch
Stage changes interactively and commit with a formatted message
Rebase a branch onto origin/main before pushing and opening a pull request

Inputs

A description of the change to be committed
A ticket ID and short description for branch naming
Details of changes, testing approach, and checklist status for a pull request

Outputs

Formatted commit messages with type, scope, subject, body, and footer
Branch names following the <type>/<ticket-id>-<short-description> format
Pull request titles and descriptions using the template in the skill

Limitations and checks

Provides guidance only; it does not execute Git commands on the user's behalf
The commit message script commit_message.py is referenced but its contents are not included in the source document
Commit messages use one of the documented types (feat, fix, docs, style, refactor, perf, test, chore) and the <type>(<scope>): <subject> format
Branch names match <type>/<ticket-id>-<short-description> as in the given examples
Pull request descriptions include Summary, Changes, Testing, and Checklist sections from the template

Search

Find projects, verify facts, compare options, and filter by your requirements

Try a searchA click only fills the search box; you stay in control

Collection Scenario Project type License Deployment Resource form

Git Workflow · Agno

Tasks

Inputs

Outputs

Limitations and checks

Search

Project Details