commit-message-generator
Generate Conventional Commit Messages
Writing clear commit messages from complex diffs can slow reviews. This skill inspects Git changes and drafts Conventional Commit messages with suggested file groups.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "commit-message-generator" from https://skillstore.io/skills/daisuke897-commit-message-generator.md and its manifest at https://skillstore.io/api/skills/daisuke897-commit-message-generator/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 "commit-message-generator". Staged changes update setup documentation and clarify install steps.
Expected outcome:
docs: update setup instructions
- Clarifies installation steps
- Adds setup notes for new contributors
Using "commit-message-generator". A diff adds a settings screen and refactors shared button styles.
Expected outcome:
Suggested split:
feat: add account settings screen
refactor: simplify shared button styles
Using "commit-message-generator". Changes fix a validation bug in the sign-in form.
Expected outcome:
fix: correct sign-in validation
- Handles empty email input
- Shows validation feedback before submit
Security Audit
SafeThe four static findings are false positives caused by Markdown backticks around Git commands. The skill uses fixed Git inspection commands to build commit suggestions and explicitly forbids running commit or push. No prompt injection or data exfiltration intent was found.
Risk Factors
⚙️ External commands (4)
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/daisuke897-commit-message-generator/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/daisuke897-commit-message-generator?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/daisuke897-commit-message-generator?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/daisuke897-commit-message-generator/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/daisuke897-commit-message-generator.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
Daisuke897. (2026). commit-message-generator security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/daisuke897-commit-message-generator/audits/8BibTeX citation
@techreport{daisuke897-daisuke897-commit-message-generator-2026,
author = {Daisuke897},
title = {commit-message-generator security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/daisuke897-commit-message-generator/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: "commit-message-generator security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Daisuke897"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/daisuke897-commit-message-generator/audits/8"
identifiers:
- type: other
value: "skillstore:daisuke897-commit-message-generator:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare Clean Commits
Generate a clear message before committing staged changes.
Split Mixed Changes
Identify separate commit groups when one diff covers several concerns.
Improve Review Context
Turn file changes into concise commit summaries for team review.
Try These Prompts
Generate a Conventional Commit message for my current Git changes. Keep it in English and do not commit anything.
Review my staged changes and suggest one Conventional Commit message with a short bullet summary.
Analyze my Git diff and tell me whether these changes should be split into multiple commits. Include target files and messages.
Generate commit suggestions that follow Conventional Commits and these project rules: [add rules]. Include rationale for any split.
Best Practices
- Stage related files before asking for a final message.
- Share project commit conventions when they differ from Conventional Commits.
- Review suggested file groups before copying any command.
Avoid
- Do not ask it to commit or push changes.
- Do not combine unrelated features and refactors into one commit.
- Do not accept a message without checking sensitive diff content.
Frequently Asked Questions
Does this skill create commits automatically?
What commit format does it use?
Can it work with staged changes?
Can it split large changes?
Does it support Claude Code?
Should I review the generated message?
Developer Details
Author
Daisuke897License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
7e9e368dc1a370f2040369ebcd0db06d90cb48e5
Maintenance freshness
7/18/2026
Usage
4 downloads · 225 views
File structure
📄 SKILL.md