Git Commit Workflow

Guides you through conventional commit formatting, explicit staging, and logical grouping of changes. Built for teams that want consistent commit history without the guesswork. The skill emphasizes staging files individually rather than using git add -A, includes a pre-commit context script that can pull in open GitHub issues for auto-linking, and provides detailed patterns for bulk-edit loops across multi-package repos. The coworker-check precondition is smart: it detects when another Claude session might have left staged files in a shared checkout, which prevents you from accidentally sweeping someone else's work into your commit. If you care about semantic versioning automation or just want your git log to stop looking like a stream of consciousness, this codifies the discipline.

skills.sh installs: 160
GitHub stars: 59
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add laurigates/claude-plugins --skill git-commit-workflow --agent claude-code

Installs into .claude/skills of the current project.

Files

Git Commit Workflow

When to Use This Skill

Use this skill when...	Use the alternative when...
Designing the conventional-commit message and staging conventions for a repo	Use `git-commit` to actually create a commit (handles pre-commit hooks, issue detection)
Reviewing how to group changes logically into focused commits	Use `git-commit-trailers` for `BREAKING CHANGE` / `Co-authored-by` trailer rules
Discussing humble, fact-based commit communication style	Use `github-issue-autodetect` to add `Fixes #N` / `Closes #N` links to messages
Authoring `feat(scope): subject` rules for your codebase	Use `github-pr-title` to apply the same conventional format to PR titles

Expert guidance for commit message conventions, staging practices, and commit best practices using conventional commits and explicit staging workflows.

For detailed examples, advanced patterns, and best practices, see REFERENCE.md.