Skill

git-commit

Creates git commits in Conventional Commits format with required type/scope/subject, enforcing project conventions from CLAUDE.md. Use for committing changes, saving work, or staging files.

Git

git-workflow

Install

npx claudepluginhub fvadicamo/dev-agent-skills --plugin github-workflow

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Creates git commits following Conventional Commits format.

Supporting Assets

references/commit_examples.md

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Stars62

Forks5

Last CommitFeb 7, 2026

Actions

View Source View Plugin View on GitHub View README

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