Agent skill · writing content · aiskillstore
git-workflow-enforcer
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.
Why this skill is useful
Provides specific validation scripts and templates for enforcing Git workflows that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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: 3. Branch Naming Common patterns: Validate: Lowercase with hyphens Prefixed with type Descriptive name Issue number if applicable: feature/123-add-dark-mode 4. Commit Message Validation Good commit: 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/PULLREQUESTTEMPLATE.md: 6. Commit Hooks Pre-commit: Commit-msg: 7. Validate Existing Commits Check recent commits for pattern adherence: 8. Generate Changelog From conventional commits: 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: Set as template: Supporting Files templates/PULLREQUESTTEMPLATE.md templates/commit-msg-hook.sh templates/.gitmessage
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/git-workflow-enforcer