mcpField
G
git-helper

git-helper

github.com/joshuadavidthomasDevelopment28762 installsUpdated today
Repository

About git-helper

A Git workflow skill for developers that covers branch management, commit conventions, and repository cleanup. It also includes scripts for branch creation, commit validation, and stale-branch cleanup.

Key features

  1. 01Create and manage branches
  2. 02Format conventional commit messages
  3. 03Prune stale remote branches
  4. 04Remove local branches
  5. 05Validate commits with helper scripts

Use cases

  1. 01Start a feature branch
  2. 02Check commit message formatting
  3. 03Clean up stale branches
  4. 04Maintain a consistent Git workflow

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/joshuadavidthomas/opencode-agent-skills --skill git-helper

After installing, type/git-helperin Claude Code to confirm it loaded.

Details

From the project README

Git Helper

A comprehensive skill for git workflow management and best practices.

Quick Start

Use this skill when you need help with:

  • Branch creation and management
  • Commit message formatting
  • Git workflow optimization
  • Repository maintenance

Common Workflows

Creating a New Feature Branch
git checkout -b feature/your-feature-name
git push -u origin feature/your-feature-name
Writing Good Commit Messages

Follow the conventional commit format:

type(scope): description

[optional body]

[optional footer]

Types: feat, fix, docs, style, refactor, test, chore

Git Cleanup Commands

Remove stale branches

git remote prune origin

Clean up local branches

git branch -d branch-name

Scripts

This skill includes helper scripts:

• create-branch.sh - Creates new feature branches with proper naming • commit-check.sh - Validates commit message format • cleanup.sh - Removes stale branches

Best Practices

  1. Always pull latest changes before creating branches
  2. Use descriptive branch names with prefixes (feature/, bugfix/, hotfix/)
  3. Write atomic commits (one logical change per commit)
  4. Keep commit messages under 72 characters for the subject line

Comments

Markdown supported