Git Workflow

VerifiedSafe

Provides guidelines for commit messages, branch naming, and pull requests following industry conventions. Helps structure Git workflows with templates and ready-to-use commands.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#git#version-control#workflow#commit#pull-request

Recommended for

Automated summary

Provides best practices for git commit messages, branch naming, and pull request creation.

Strengths

  • Standardizes commit format
  • Encourages conventional commits
  • Provides branch naming conventions
  • Includes PR templates

Limitations

  • Assumes a specific commit format may not suit all teams
  • Requires manual adherence
  • Doesn't automate any process
When to use it

When you want to enforce consistent git workflow practices across a team.

When not to use it

When your team already has a well-established git workflow that differs from these conventions.

Security analysis

Safe
Quality score85/100

The skill provides guidance on git workflows and includes example bash commands like git checkout, commit, and push. These are standard operations with no destructive or exfiltrating instructions. The reference to get_skill_script does not itself execute anything malicious; it simply suggests using a helper script for commit messages. No dangerous tools or patterns are present.

No concerns found

How this analysis is made

Examples

Generate commit message
I changed the login page to support OAuth2. Write a commit message.
Create branch name
Create a branch for ticket JIRA-456 that fixes a null pointer bug.
Review PR description
Review this pull request description and suggest improvements.

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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/git-workflow-mmlj2nkx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/git-workflow-mmlj2nkx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-workflow-mmlj2nkx/download' --output '.skill-downloads/git-workflow-mmlj2nkx/SKILL.md.part' && mv '.skill-downloads/git-workflow-mmlj2nkx/SKILL.md.part' '.skill-downloads/git-workflow-mmlj2nkx/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/git-workflow-mmlj2nkx/SKILL.md' && test -s '.skill-downloads/git-workflow-mmlj2nkx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/git-workflow' && cp -R '.skill-downloads/git-workflow-mmlj2nkx' '.claude/skills/git-workflow'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/git-workflow-mmlj2nkx'

openskills read 'git-workflow-mmlj2nkx'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/git-workflow-mmlj2nkx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills