LLM Skills
~/catalog/debugging & maintenance//commit

Smart Git Commit

/commit

I'll analyze your changes and create a meaningful commit message.

notlikeDevnotlikeDev
2.8k
October 7, 2025
MIT License
// skill content

Smart Git Commit I'll analyze your changes and create a meaningful commit message. Pre-Commit Quality Checks: Before committing, I'll verify: - Build passes (if a build command exists) - Tests pass (if a test command exists) - Linter passes (if a lint command exists) - No obvious errors in the changed files First, let me check if this is a Git repository and what has changed: ``bash # Verify we're in a git repository if ! git rev-parse --git-dir > /dev/null 2>&1; then echo "Error: Not a git repository" echo "This command requires git version control" exit 1 fi # Check if we have changes to commit if ! git diff --cached --quiet || ! git diff --quiet; then echo "Changes detected:" git status --short else echo "No changes to commit" exit 0 fi # Show detailed changes git diff --cached --stat git diff --stat Now I'll analyze the changes to determine: 1. What files were modified 2. The nature of changes (feature, fix, refactor, etc.) 3. The scope/component affected If the analysis or commit encounters errors: - I'll explain what went wrong - Suggest how to resolve it - Ensure no partial commits occur bash # If nothing is staged, I'll stage modified files (not untracked) if git diff --cached --quiet; then echo "No files staged. Staging modified files..." git add -u fi # Show what will be committed git diff --cached --name-status Based on the analysis, I'll create a conventional commit message: - **Type**: feat|fix|docs|style|refactor|test|chore - **Scope**: component or area affected (optional) - **Subject**: clear description in present tense - **Body**: why the change was made (if needed) bash # I'll create the commit with the analyzed message # Example: git commit -m "fix(auth): resolve login timeout issue" `` The commit message will be concise, meaningful, and follow your project’s conventions if I can detect them from recent commits. Important: I will NEVER: - Add “Co-authored-by” or any Claude signatures - Include "Generated with Claude Code" or similar messages - Modify git config or user credentials - Add any AI/assistant attribution to the commit - Use emojis in commits, PRs, or git-related content The commit will use only your existing git user configuration, maintaining full ownership and authenticity of your commits.

// original public source
notlikeDev/CCPlugins
/commands/commit.md
License: MIT License
Independent project, not affiliated with Anthropic. This skill remains the property of its original author.
// install this skill
Paste this command in your terminal at the root of your project:
mkdir -p .claude/commands && curl -o ".claude/commands/commit.md" "https://raw.githubusercontent.com/notlikeDev/CCPlugins/main/commands/commit.md"
Then in Claude Code, type /commit to activate it.
open_in_newOpen original source
// save
Save available after sign in.
loginSign in to save
// information
CreatornotlikeDev
Stars 2.8k
LicenseMIT License
UpdatedOctober 7, 2025
Format.md
AccessFree
// similar

Skills Debugging & maintenance

View allarrow_forward