git-commit-message
Write Clear Git Commit Messages
Vague commit messages make change history difficult to understand. This skill uses staged changes to draft typed subjects and optional bodies explaining the reason.
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "git-commit-message" from https://skillstore.io/skills/alapha888-git-commit-message.md and its manifest at https://skillstore.io/api/skills/alapha888-git-commit-message/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「git-commit-message」。 Staged changes preserve order-list filters when moving between pages.
預期結果:
- Subject: fix: keep order-list filters across pagination
- Body: Preserve selected filters when users move between pages.
正在使用「git-commit-message」。 Staged documentation changes clarify the local setup steps.
預期結果:
- Subject: docs: clarify local setup steps
- Body: Explain required setup steps before starting development.
安全審計
安全All 17 static findings are false positives: Markdown formatting, task-related Git commands, and explanatory commit text do not establish malicious execution or reconnaissance. No evidence found of prompt injection, credential access, or data exfiltration in SKILL.md. The skill generates commit commands, which users should review before execution.
風險因素
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/alapha888-git-commit-message/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/alapha888-git-commit-message?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/alapha888-git-commit-message?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/alapha888-git-commit-message/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/alapha888-git-commit-message.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
alapha888. (2026). git-commit-message security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/alapha888-git-commit-message/audits/1BibTeX 引用
@techreport{alapha888-alapha888-git-commit-message-2026,
author = {alapha888},
title = {git-commit-message security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/alapha888-git-commit-message/audits/1},
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-message security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "alapha888"
date-released: "2026-10-06"
url: "https://skillstore.io/skills/alapha888-git-commit-message/audits/1"
identifiers:
- type: other
value: "skillstore:alapha888-git-commit-message:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Summarize a Bug Fix
Turn a staged fix into a concise subject and a body describing the conditions that triggered the bug.
Record Documentation Changes
Generate a docs message that identifies the updated guidance without adding unsupported implementation claims.
Review Mixed Changes
Identify staged changes that combine commit types and request separate commits before drafting messages.
試試這些提示
Generate a commit message from my staged changes. Check staging first and provide the suggested Git commit command without executing it.
Inspect my staged bug fix. Write a fix subject and a short body stating the trigger conditions supported by the diff.
Review my staged changes for mixed commit types. Ask me to split unrelated changes before producing a final commit command.
Inspect staged changes and draft one typed subject under 50 characters. Explain why in the body and safely quote shell arguments. Do not execute.
最佳實務
- Stage only the changes intended for the commit before requesting a message.
- Check that the subject and body describe evidence from the actual diff.
- Review generated commands and shell quoting before execution.
避免
- Requesting a message when no changes are staged.
- Using chore for every feature or bug fix.
- Combining unrelated changes under one vague subject.