git-commit
Create Clear Conventional Git Commits
Inconsistent commits make project history difficult to review and maintain. This skill analyzes changes, stages logical groups, and creates standardized 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" from https://skillstore.io/skills/github-git-commit.md and its manifest at https://skillstore.io/api/skills/github-git-commit/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". Commit the staged authentication bug fix.
Expected outcome:
Created commit: fix(auth): reject expired sessions
Using "git-commit". Commit the new export endpoint and reference issue 84.
Expected outcome:
Created feature commit for the API export endpoint with footer: Closes #84
Using "git-commit". Separate documentation changes from test updates.
Expected outcome:
- Created documentation commit for the setup guide.
- Created test commit for authentication coverage.
Security Audit
SafeAll 28 static findings are false positives. Backticks are Markdown formatting, the here-document invokes local cat with a quoted delimiter, and sensitive filenames appear only in a warning. No prompt injection or harmful intent was found.
Risk Factors
⚙️ External commands (25)
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/github-git-commit/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/github-git-commit?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/github-git-commit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/github-git-commit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/github-git-commit.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
github. (2026). git-commit security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/github-git-commit/audits/8BibTeX citation
@techreport{github-github-git-commit-2026,
author = {github},
title = {git-commit security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/github-git-commit/audits/8},
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 security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "github"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/github-git-commit/audits/8"
identifiers:
- type: other
value: "skillstore:github-git-commit:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
4 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
21pounder-git-commit
2026-08-21
chemiseblanc-git-commit
2026-08-21
github-git-commit
2026-08-21
bae-changhyun-git-commit
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Commit a focused feature
Review changes, stage related files, and create a clear feature commit.
Standardize project history
Apply consistent types, scopes, descriptions, and issue references across contributions.
Document a breaking change
Create a commit with a breaking-change marker, explanatory body, and footer.
Try These Prompts
Review my staged changes, propose a Conventional Commit message, and create the commit.
Inspect my changes, stage only files for one logical update, propose a message, and commit them.
Create a fix commit for the auth scope, derive its description from the diff, and add Closes #123.
Divide my changes into logical groups, explain each group, then create separate Conventional Commits after confirmation.
Best Practices
- Review staged files and the proposed message before creating each commit.
- Keep each commit limited to one logical change.
- Use imperative descriptions under 72 characters and include relevant issue references.
Avoid
- Do not stage secret files, credentials, private keys, or unrelated changes.
- Do not bypass hooks or use destructive Git commands without explicit approval.
- Do not combine unrelated features, fixes, and maintenance work in one commit.