agentskills.codes
GI

git-workflow-enforcer

by CrazyDubyaCodingSource

Standardizes git operations by verifying branch names, commit messages, and PR templates.

GitCode Review

Install

mkdir -p .claude/skills/git-workflow-enforcer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/333" && unzip -o skill.zip -d .claude/skills/git-workflow-enforcer && rm skill.zip

Installs to .claude/skills/git-workflow-enforcer

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.
170 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • →Enforce conventional commit message formats
  • →Validate branch naming conventions
  • →Check pull request template adherence
  • →Suggest commit hooks for pre-commit and commit-msg
  • →Generate changelogs from conventional commits

How it works

This skill enforces consistent Git workflows by checking commit messages against conventional commit formats, validating branch names, and ensuring pull requests follow specified templates.

Inputs & outputs

You give it
Git commits, branches, or pull requests
You get back
Validation feedback or formatted git artifacts

When to use git-workflow-enforcer

  • →Validating commit messages
  • →Enforcing branch naming
  • →Checking pull request templates
  • →Preparing for code review

About this skill

Git Workflow Enforcer

Enforces consistent Git workflows including commit messages, branch naming, and PR processes.

When to Use

  • Creating commits or branches
  • Code review or PR creation
  • User mentions "git workflow", "commit message", "branch naming", or "pull request"

Instructions

1. Detect Existing Conventions

Check for:

  • .github/ or .gitlab/ templates
  • CONTRIBUTING.md
  • Existing commit message patterns
  • Branch naming patterns

2. Conventional Commits

Format: type(scope): description

Types:

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation
  • style: Formatting, missing semicolons
  • refactor: Code restructuring
  • perf: Performance improvement
  • test: Adding tests
  • chore: Maintenance, dependencies

Examples:

feat(auth): add OAuth2 login support
fix(api): handle null response in user endpoint
docs(readme): update installation instructions
refactor(utils): simplify date formatting logic

3. Branch Naming

Common patterns:

feature/user-authentication
bugfix/login-error-handling
hotfix/critical-security-patch
release/v1.2.0
chore/update-dependencies

Validate:

  • Lowercase with hyphens
  • Prefixed with type
  • Descriptive name
  • Issue number if applicable: feature/123-add-dark-mode

4. Commit Message Validation

Good commit:

feat(payments): integrate Stripe payment gateway

- Add Stripe SDK configuration
- Implement payment intent creation
- Add webhook handler for payment events
- Update tests for payment flow

Closes #456

Check for:

  • Subject line ≤50 characters
  • Body wrapped at 72 characters
  • Blank line between subject and body
  • Imperative mood ("add" not "added")
  • Reference to issue/ticket

5. PR Template

Create .github/PULL_REQUEST_TEMPLATE.md:

## Description
<!-- What does this PR do? -->

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation update

## Testing
<!-- How was this tested? -->

## Checklist
- [ ] Code follows project style guidelines
- [ ] Self-review completed
- [ ] Comments added for complex code
- [ ] Documentation updated
- [ ] Tests added/updated
- [ ] All tests passing
- [ ] No new warnings

## Related Issues
Closes #

6. Commit Hooks

Pre-commit:

#!/bin/sh
# .git/hooks/pre-commit

# Run linter
npm run lint

# Run tests
npm test

# Check for sensitive data
if git diff --cached | grep -i "password\|api_key\|secret"; then
  echo "Error: Possible sensitive data detected"
  exit 1
fi

Commit-msg:

#!/bin/sh
# .git/hooks/commit-msg

commit_msg=$(cat "$1")

# Check conventional commit format
if ! echo "$commit_msg" | grep -qE "^(feat|fix|docs|style|refactor|perf|test|chore)(\(.+\))?: .+"; then
  echo "Error: Commit message must follow Conventional Commits format"
  echo "Example: feat(auth): add login feature"
  exit 1
fi

7. Validate Existing Commits

Check recent commits for pattern adherence:

git log --oneline -20 | grep -v "^[a-f0-9]\{7\} (feat|fix|docs|style|refactor|perf|test|chore)"

8. Generate Changelog

From conventional commits:

# Using standard-version
npx standard-version

# Or manually group by type
git log --pretty=format:"%s" | grep "^feat" > features.txt
git log --pretty=format:"%s" | grep "^fix" > fixes.txt

9. Protected Branches

GitHub settings:

  • Require PR reviews
  • Require status checks
  • Require signed commits
  • Restrict who can push
  • Require linear history

10. Best Practices

  • Atomic commits: One logical change per commit
  • Descriptive messages: Explain why, not what
  • Frequent commits: Small, frequent over large, rare
  • Clean history: Squash/rebase before merge
  • Sign commits: GPG signature for security
  • Reference issues: Link to tracking system

Git Commit Template

Create .gitmessage:

<type>(<scope>): <subject>

<body>

<footer>

# Type: feat, fix, docs, style, refactor, perf, test, chore
# Scope: component or file affected
# Subject: imperative, lowercase, no period, ≤50 chars
# Body: explain what and why, not how, wrapped at 72 chars
# Footer: breaking changes, issue references

Set as template:

git config --global commit.template ~/.gitmessage

Supporting Files

  • templates/PULL_REQUEST_TEMPLATE.md
  • templates/commit-msg-hook.sh
  • templates/.gitmessage

How it compares

This skill automates the enforcement of specific Git workflow rules, such as subject line length and imperative mood for commit messages, which manual processes might miss.

Compared to similar skills

git-workflow-enforcer side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
git-workflow-enforcer (this skill)89moReviewIntermediate
resolve-conflicts818moReviewIntermediate
dependency-upgrade265moReviewIntermediate
git-commits214moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

resolve-conflicts

antinomyhq

Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.

81334

dependency-upgrade

wshobson

Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.

26240

git-commits

bonny

Create well-structured git commits in logical chunks following best practices

21109

git-advanced-workflows

wshobson

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

1197

github-multi-repo

ruvnet

Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration

696

gh-address-comments

openai

Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.

1059

Search skills

Search the agent skills registry