Git Commit Helper
Write Clear Git Commit Messages
Vague commits make reviews and release notes harder. This skill analyzes staged Git changes and drafts structured Conventional Commit messages.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "Git Commit Helper" from https://skillstore.io/skills/davila7-git-commit-helper.md and its manifest at https://skillstore.io/api/skills/davila7-git-commit-helper/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "Git Commit Helper". Staged changes add password reset email flow and tests.
Expected outcome:
Suggested message: feat(auth): add password reset email flow. Body: Explain the new email flow and test coverage.
Using "Git Commit Helper". Staged changes fix a crash when profile data is missing.
Expected outcome:
Suggested message: fix(profile): handle missing user data. Body: Add null checks and cover the empty-state path.
Using "Git Commit Helper". Staged changes update API response format and client parsing.
Expected outcome:
Suggested message: feat(api)!: standardize response format. Body: Include a breaking change note for clients.
Security Audit
SafeTwenty-seven external-command alerts are false positives caused by Markdown fences, inline code, and documented Git commands; none execute from the skill text. The three line 9 alerts are confirmed because a PostToolUse hook runs shell commands after every Bash action and appends to a hidden home-directory log. No prompt injection, credential access, network activity, or data exfiltration intent was found.
Capability review items (3)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (28)
📁 Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/davila7-git-commit-helper/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/davila7-git-commit-helper?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/davila7-git-commit-helper?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/davila7-git-commit-helper/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/davila7-git-commit-helper.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
davila7. (2026). Git Commit Helper security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/davila7-git-commit-helper/audits/9BibTeX citation
@techreport{davila7-davila7-git-commit-helper-2026,
author = {davila7},
title = {Git Commit Helper security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/davila7-git-commit-helper/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "Git Commit Helper security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "davila7"
date-released: "2026-07-19"
url: "https://skillstore.io/skills/davila7-git-commit-helper/audits/9"
identifiers:
- type: other
value: "skillstore:davila7-git-commit-helper:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
89jobrien-git-commit-helper
2026-08-21
davila7-git-commit-helper
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Daily Feature Work
Turn staged feature changes into a concise commit summary and explanatory body.
Review Cleanup
Split noisy staged changes into clearer commit types and scopes before review.
Release Preparation
Mark breaking changes and write commit bodies that support changelog generation.
Try These Prompts
Review my staged changes and suggest one Conventional Commit message with a short body.
Compare these staged changes and choose the best commit type and scope before drafting the message.
Help split my staged diff into atomic commits and write messages for each logical change.
Audit this staged diff for breaking changes, issue references, and release-note wording before writing the final commit message.
Best Practices
- Stage one logical change before asking for a commit message.
- Review the proposed type, scope, and summary before committing.
- Add context about issue numbers, breaking changes, and user impact.
Avoid
- Do not ask it to commit, amend, or stage files without reviewing the command first.
- Do not combine unrelated changes into one generated message.
- Do not paste secrets or private diffs into shared conversations.