Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
fvadicamo avatar

Git Commit

  • 299 installs
  • 69 repo stars
  • Updated August 4, 2026
  • fvadicamo/dev-agent-skills

git-commit is a Claude Code agent skill that creates Conventional Commits with required scopes, HEREDOC bodies, and project-specific rules from CLAUDE.md for developers who need consistent git history before pull request

About

git-commit is an agent skill from fvadicamo/dev-agent-skills that automates staging, diff scoping, and Conventional Commits formatting before developers open or update pull requests. The skill reads CLAUDE.md for project-specific commit conventions, loads recent commit history for style matching, and enforces required kebab-case scopes, imperative subjects capped at 50 characters, and a security commit type beyond standard Conventional Commits. It provides HEREDOC patterns for multi-line bodies that link requirements and tasks, blocks vague messages like fix bug, and supports both regular branch commits and merge commits for PR closure. Developers reach for git-commit when they want machine-readable history compatible with semantic versioning and automated changelogs without memorizing team commit rules each session.

  • Conventional commit message formatting guidance
  • Staged-change review before committing
  • Atomic commits with focused scope
  • Hooks and policy awareness for safe commits
  • Prepares history for easier PR review

Git Commit by the numbers

  • 299 all-time installs (skills.sh)
  • Ranked #139 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/fvadicamo/dev-agent-skills --skill git-commit

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs299
repo stars69
Last updatedAugust 4, 2026
Repositoryfvadicamo/dev-agent-skills

How do you enforce Conventional Commits before pull requests?

Produce clean, conventional git commits with accurate messages, scoped diffs, and pre-commit checks before opening or updating pull requests.

Who is it for?

Developers on teams that require scoped Conventional Commits, readable history, and pre-PR commit hygiene.

Skip if: Developers who only need ad-hoc commits without format enforcement or who already use fully automated release bots for every change.

When should I use this skill?

The user asks to commit changes, stage files, write a commit message, or save work before a pull request.

What you get

Scoped git commits with Conventional Commits subjects, optional multi-line HEREDOC bodies, and merge-ready history.

  • conventional git commit
  • scoped diff summary

By the numbers

  • Enforces 50-character maximum Conventional Commits subject lines
  • Adds security commit type beyond standard Conventional Commits
  • Uses HEREDOC pattern for multi-line commit bodies

Files

SKILL.mdMarkdownGitHub ↗

Git commit

Creates git commits following Conventional Commits format.

Recent project commits

!git log --oneline -5 2>/dev/null

Quick start

# 1. Stage changes
git add <files>

# 2. Create commit
git commit -m "type(scope): subject"

Project conventions

  • Scope is required (kebab-case): validation, auth, cookie-service, api
  • Additional type beyond standard CC: security (vulnerability fixes or hardening)
  • HEREDOC for multi-line commits:
git commit -m "$(cat <<'EOF'
feat(validation): add URLValidator with domain whitelist

Implement URLValidator class supporting:
- Domain whitelist enforcement
- Dangerous scheme blocking

Addresses Requirement 31
Part of Task 5.1
EOF
)"

Important rules

  • ALWAYS check CLAUDE.md conventions first - use project format if it differs
  • ALWAYS include scope in parentheses
  • ALWAYS use present tense imperative verb for the subject
  • NEVER end subject with a period
  • NEVER exceed 50 chars in the subject line
  • NEVER use generic messages ("update code", "fix bug", "changes")
  • Group related changes into a single focused commit

References

  • references/commit_examples.md - Extended examples by type, good/bad comparisons

Related skills

How it compares

Pick git-commit over generic commit helpers when the team needs enforced scopes, CLAUDE.md-aware conventions, and PR-ready Conventional Commits history.

FAQ

What commit format does git-commit enforce?

git-commit enforces Conventional Commits as type(scope): subject with a required kebab-case scope, imperative subject under 50 characters, no trailing period, and an extra security type for vulnerability fixes beyond standard CC types.

Does git-commit read project-specific rules?

git-commit checks CLAUDE.md first for project commit conventions and inspects recent repository commits so new messages match the team's established style instead of generic update code subjects.

When should developers use git-commit?

git-commit activates when developers want to stage changes, create a commit, save work, or prepare commits before opening or updating a pull request with consistent Conventional Commits formatting.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.