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.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
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.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "git-commit-message". Staged changes preserve order-list filters when moving between pages.
Resultado esperado:
- Subject: fix: keep order-list filters across pagination
- Body: Preserve selected filters when users move between pages.
Usando "git-commit-message". Staged documentation changes clarify the local setup steps.
Resultado esperado:
- Subject: docs: clarify local setup steps
- Body: Explain required setup steps before starting development.
Auditoría de seguridad
SeguroAll 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.
Factores de riesgo
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/alapha888-git-commit-message/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/alapha888-git-commit-message?utm_source=security_passport_badge)Insignia 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>Tarjeta para insertar
<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>Citas académicas (APA · BibTeX · CFF)
Cita 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/1Cita BibTeX
@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"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
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.
Prueba estos prompts
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.
Mejores prácticas
- 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.
Evitar
- Requesting a message when no changes are staged.
- Using chore for every feature or bug fix.
- Combining unrelated changes under one vague subject.