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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「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.