Intelligently analyzes changes and creates well-formatted git commits with conventional commit messages
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
78
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
Safety & privacy surface
1 safety and 1 privacy notes across 2 risk areas. Review closely: network access.
/git-smart-commit feat "add structured content schema"git status --shortgit diff --cached --statgit diff --statgit log --oneline -5Analyze the changes and create a git commit following these guidelines:
Conventional Commit Format:
Commit Message Structure:
<type>(<scope>): <subject>
<body>
<footer>
Best Practices:
Smart Analysis:
If arguments provided: Use $1 as type and $2 as message. Otherwise: Analyze changes and suggest appropriate commit.
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
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.
[](https://heyclau.de/entry/commands/git-smart-commit)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 status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed |
| SubmitterDiffers | — | jony376 |
| Install risk | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — |
| Category | commands | commands |
| Source | Source-backed | Source-backed |
| Author | JSONbored | jony376 |
| Added | 2025-09-15 | 2026-06-04 |
| Platforms | ||
| Harness | ||
| Source repo | — | — |
| Safety notes | ✓Creates 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 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. | ✓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 | — | |
| Config | — | — |
| Citations | ||
| Claim | Unclaimed | Unclaimed |
Maintainer workflow bundle for CI triage, PR review, commit governance, releases, and workflow validation.
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.