Skill

git-commit

This skill should be used when creating conventional commits for current changes. It groups related changes into logical commits, ensures all files are committed, and verifies the working directory is clean afterward.

Install

npx claudepluginhub codyswanngt/lisa --plugin lisa

Tool Access

This skill is limited to using the following tools:

Bash

Preview

Create conventional commits for current changes. Optional hint: $ARGUMENTS

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

Parent Repo Stars1

Parent Repo Forks2

Last CommitMar 5, 2026

Actions

View Source View Plugin View on GitHub View README

Git Commit Workflow

Create conventional commits for current changes. Optional hint: $ARGUMENTS

Workflow

See what has changed

!git status !git diff --stat

Apply these requirements

Branch Check: If on dev, staging, or main, create a feature branch named after the changes

Commit Strategy: Group related changes into logical conventional commits (feat, fix, chore, docs, etc.)

Commit ALL Files: Every file must be assigned to a commit group - no file gets left out or unstaged

Commit Creation: Stage and commit each group with clear messages

Verification: Run git status to confirm working directory is clean - must show "nothing to commit"

Use conventional commit format

feat: for new features

fix: for bug fixes

docs: for documentation

chore: for maintenance

style: for formatting

refactor: for code restructuring

test: for test additions

Never

use --no-verify flag

attempt to bypass tests or quality checks

skip tests or quality checks

stash changes - ALL changes must be committed

skip or exclude any files from the commit - even if they're unrelated

leave uncommitted changes in the working directory

ask the user which files to commit - commit everything

Execute

Execute the workflow now.

Git Commit Workflow

Create conventional commits for current changes. Optional hint: $ARGUMENTS

Workflow

See what has changed

!git status !git diff --stat

Apply these requirements

Branch Check: If on dev, staging, or main, create a feature branch named after the changes
Commit Strategy: Group related changes into logical conventional commits (feat, fix, chore, docs, etc.)
Commit ALL Files: Every file must be assigned to a commit group - no file gets left out or unstaged
Commit Creation: Stage and commit each group with clear messages
Verification: Run git status to confirm working directory is clean - must show "nothing to commit"

Use conventional commit format

feat: for new features
fix: for bug fixes
docs: for documentation
chore: for maintenance
style: for formatting
refactor: for code restructuring
test: for test additions

Never

use --no-verify flag
attempt to bypass tests or quality checks
skip tests or quality checks
stash changes - ALL changes must be committed
skip or exclude any files from the commit - even if they're unrelated
leave uncommitted changes in the working directory
ask the user which files to commit - commit everything

Execute

Execute the workflow now.