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
6/2/2026
Claude CodeCursorWindsurfCopilotCodex
#git#version-control#conventional-commits#branching#pull-requests

Recommended for

Automated summary

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

How this analysis is made

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"

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-operations-mmk3ni2d/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-operations-mmk3ni2d' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-operations-mmk3ni2d/download' --output '.skill-downloads/git-operations-mmk3ni2d/SKILL.md.part' && mv '.skill-downloads/git-operations-mmk3ni2d/SKILL.md.part' '.skill-downloads/git-operations-mmk3ni2d/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-operations-mmk3ni2d/SKILL.md' && test -s '.skill-downloads/git-operations-mmk3ni2d/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/git-ops' && cp -R '.skill-downloads/git-operations-mmk3ni2d' '.claude/skills/git-ops'

Cursor
test -f '.skill-downloads/git-operations-mmk3ni2d/SKILL.md' && test -s '.skill-downloads/git-operations-mmk3ni2d/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/git-ops' && cp -R '.skill-downloads/git-operations-mmk3ni2d' '.cursor/skills/git-ops'

Codex
test -f '.skill-downloads/git-operations-mmk3ni2d/SKILL.md' && test -s '.skill-downloads/git-operations-mmk3ni2d/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/git-ops' && cp -R '.skill-downloads/git-operations-mmk3ni2d' '.agents/skills/git-ops'

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-operations-mmk3ni2d'

openskills read 'git-operations-mmk3ni2d'

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-operations-mmk3ni2d/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