Git Operations

VerifiedSafe

Handles Git operations including commits with conventional format, branch naming per GitFlow/GitHub Flow, pull request creation with templates, and conflict resolution. Helps maintain consistent Git workflows by automating commit message generation and enforcing standard patterns.

Sby Skills Guide Bot
DevelopmentIntermediate
806/2/2026
Claude CodeCursorWindsurfCopilotCodex
#git#version-control#conventional-commits#branching#pull-requests

Recommended for

Our review

This skill handles common Git operations following conventional commits and GitFlow/GitHub Flow workflows.

Strengths

  • Standardizes commit messages and branch naming
  • Simplifies pull request creation with templates
  • Provides structured conflict resolution steps
  • Works across any AI tool that supports shell and Git

Limitations

  • Requires terminal access for the AI tool
  • Cannot fully automate complex conflict resolution
  • Depends on existing Git configuration (hooks, etc.)
When to use it

Use this skill for any repetitive or structured Git operation such as commits, branches, PRs, or conflict resolution.

When not to use it

Avoid using it for advanced, highly specific Git operations (e.g., heavy interactive rebase, git bisect) or when you need full manual control.

Security analysis

Safe
Quality score88/100

This skill uses standard git commands and shell for git operations like branching, committing, and PR creation. No destructive or exfiltrating actions are instructed. The declared tools (git, shell) are used for their legitimate purposes, and no sensitive data exposure is indicated. The smart_commit.sh script is not provided but likely benign.

No concerns found

Examples

Create feature branch and commit
Create a new feature branch named 'feature/AUTH-123-user-login' and commit changes with a conventional commit message of type 'feat' and scope 'auth'.
Create a pull request
Create a pull request from branch 'feature/AUTH-123-user-login' to 'main' with a descriptive title, fill in the PR template, and request review from the team.
Resolve a merge conflict
I have a merge conflict in 'src/app.js' between 'main' and 'feature/user-profile'. Please help me resolve it by fetching the latest changes, identifying conflict sources, and preserving both intents.

name: git-ops description: Git operations including commits, branches, PRs, and conflict resolution version: 1.0.0 author: Vertice Agency tools:

  • git
  • shell

Git Operations Skill

Overview

Handle all Git-related operations following conventional commits and GitFlow/GitHub Flow patterns.

Instructions

Commit Message Format

<type>(<scope>): <description>

[optional body]

[optional footer]

Types:

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation
  • style: Formatting
  • refactor: Code restructuring
  • test: Adding tests
  • chore: Maintenance

Branch Naming

  • feature/<ticket>-<description>
  • fix/<ticket>-<description>
  • hotfix/<description>
  • release/<version>

PR Creation

  1. Create descriptive title
  2. Fill PR template
  3. Link related issues
  4. Add appropriate labels
  5. Request reviewers

Conflict Resolution

  1. Fetch latest changes
  2. Identify conflict sources
  3. Resolve preserving both intents
  4. Test after resolution
  5. Commit with clear message

Scripts

smart_commit.sh

Generates commit message from diff analysis.

pr_template.md

Standard PR template.

Examples

Create feature branch and commit

git checkout -b feature/AUTH-123-user-login
# ... make changes ...
git add .
git commit -m "feat(auth): implement user login with JWT"
Related skills