Skip to main content
commandsSource-backedReview first Safety Privacy

Git Smart Commit for Claude Code

Intelligently analyzes changes and creates well-formatted git commits with conventional commit messages

by JSONbored·added 2025-09-15·
HarnessClaude Code
Invocation:/git-smart-commit [type] [message]
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://www.conventionalcommits.org/, https://github.com/JSONbored/awesome-claude/blob/main/content/commands/git-smart-commit.mdx
Safety notes
Creates git commits in your repository from the staged changes; review the generated commit before pushing.
Privacy notes
Reads your staged changes, diffs, and branch and repository metadata to draft a commit message; that content is sent to the model as part of the request and is not written or transmitted anywhere else.
Author
JSONbored
Claim status
unclaimed
Last verified
2025-09-15

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Install command

Not provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

None

Platforms

1 listed

Difficulty

24/100

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: network access.

2 areas
  • SafetyGeneralCreates git commits in your repository from the staged changes; review the generated commit before pushing.
  • PrivacyNetwork accessReads your staged changes, diffs, and branch and repository metadata to draft a commit message; that content is sent to the model as part of the request and is not written or transmitted anywhere else.

Safety notes

  • Creates git commits in your repository from the staged changes; review the generated commit before pushing.

Privacy notes

  • Reads your staged changes, diffs, and branch and repository metadata to draft a commit message; that content is sent to the model as part of the request and is not written or transmitted anywhere else.

Schema details

Install type
copy
Reading time
2 min
Difficulty score
24
Troubleshooting
Yes
Breaking changes
No
Runtime and command metadata
Command syntax
/git-smart-commit [type] [message]
Argument hint
[type] [message]
Allowed tools
Bash(git add:*)Bash(git status:*)Bash(git diff:*)Bash(git commit:*)
Full copyable content
/git-smart-commit feat "add structured content schema"

About this resource

Context

  • Current git status: !git status --short
  • Staged changes: !git diff --cached --stat
  • Unstaged changes: !git diff --stat
  • Recent commits: !git log --oneline -5

Your Task

Analyze the changes and create a git commit following these guidelines:

  1. Conventional Commit Format:

    • feat: New feature
    • fix: Bug fix
    • docs: Documentation changes
    • style: Code style changes (formatting, etc)
    • refactor: Code refactoring
    • perf: Performance improvements
    • test: Test changes
    • build: Build system changes
    • ci: CI/CD changes
    • chore: Other changes
  2. Commit Message Structure:

    <type>(<scope>): <subject>
    
    <body>
    
    <footer>
    
  3. Best Practices:

    • Subject line: 50 characters max
    • Use imperative mood ("Add" not "Added")
    • Body: Wrap at 72 characters
    • Explain what and why, not how
    • Reference issues if applicable
  4. Smart Analysis:

    • Group related changes
    • Suggest splitting if changes are unrelated
    • Detect breaking changes
    • Identify files that shouldn't be committed

If arguments provided: Use $1 as type and $2 as message. Otherwise: Analyze changes and suggest appropriate commit.

Command Metadata

allowed-tools:
  - Bash(git add:*)
  - Bash(git status:*)
  - Bash(git diff:*)
  - Bash(git commit:*)
argument-hint: [type] [message]
description: Create a smart git commit
model: sonnet

Steps

  1. Review all changes
  2. Identify the commit type
  3. Stage appropriate files
  4. Create descriptive commit message
  5. Commit the changes

Source citations

Add this badge to your README

Show that Git Smart Commit for Claude Code is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/commands/git-smart-commit.svg)](https://heyclau.de/entry/commands/git-smart-commit)

How it compares

Git Smart Commit for Claude Code side by side with its closest alternative on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field

Intelligently analyzes changes and creates well-formatted git commits with conventional commit messages

Open dossier

Slash command that drafts release notes from the Conventional Commits made since the last release tag.

Open dossier
Next stepsDiffers
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backed
SubmitterDiffersjony376
Install riskReview firstReview first
Notes Safety Privacy Safety Privacy
Brand
Categorycommandscommands
Sourcesource-backedsource-backed
AuthorJSONboredjony376
Added2025-09-152026-06-04
Platforms
Claude Code
Claude Code
Source repo
Safety notesCreates git commits in your repository from the staged changes; review the generated commit before pushing.Read-only with respect to your repository when refs are validated and passed as git arguments; it only reads git history (tags and commit log) and never creates tags, commits, branches, or release artifacts. Validate the optional ref or discovered tag with `git rev-parse --verify --quiet <ref>^{commit}` and reject refs containing shell metacharacters before reading history. It proposes a version bump and notes for you to review; it does not publish a release or push anything.
Privacy notesReads your staged changes, diffs, and branch and repository metadata to draft a commit message; that content is sent to the model as part of the request and is not written or transmitted anywhere else.Commit subjects, bodies, and author names from the selected range are included in the model's context to draft the notes. If commit messages contain internal identifiers, customer names, or unreleased details, those become part of the prompt; review the range before running on a private history. The command writes nothing to disk on its own.
Prerequisites— none listed— none listed
Install
/draft-release-notes [from-ref]
Config
Citations
ClaimUnclaimedUnclaimed
Open in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.