commit-drafter
Draft Git Commit Messages From Staged Changes
Writing commit messages from staged changes takes time and can miss important context. This skill collects git status and diff details so AI can draft a clear message.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "commit-drafter" from https://skillstore.io/skills/abejitsu-commit-drafter.md and its manifest at https://skillstore.io/api/skills/abejitsu-commit-drafter/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-drafter". User asks for a draft after staging authentication test updates.
Expected outcome:
Update authentication tests
What: Add coverage for expired sessions.
Why: Prevent regressions in login behavior.
How: Add assertions for redirects and error handling.
Using "commit-drafter". User asks for a draft after staging documentation edits.
Expected outcome:
Improve setup documentation
What: Clarify installation steps and configuration notes.
Why: Help new contributors start faster.
How: Reorder instructions and add missing context.
Using "commit-drafter". User asks for a draft after staging a small bug fix.
Expected outcome:
Fix profile save error
What: Handle missing display names during profile updates.
Why: Avoid failed saves for existing accounts.
How: Apply a fallback value before validation.
Security Audit
SafeBoth static findings were adjudicated as false positives. drafter.py uses subprocess.run for fixed git commands without shell execution, and SKILL.md contains markdown backticks only. No evidence found of prompt injection text, data exfiltration intent, network calls, or malicious behavior.
Risk Factors
⚙️ External commands (2)
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/abejitsu-commit-drafter/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/abejitsu-commit-drafter?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/abejitsu-commit-drafter?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/abejitsu-commit-drafter/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/abejitsu-commit-drafter.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
abereyes. (2026). commit-drafter security audit report (audit version 9) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/abejitsu-commit-drafter/audits/9BibTeX citation
@techreport{abereyes-abejitsu-commit-drafter-2026,
author = {abereyes},
title = {commit-drafter security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/abejitsu-commit-drafter/audits/9},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "commit-drafter security audit report (audit version 9)"
version: "1.0.0"
type: report
authors:
- name: "abereyes"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/abejitsu-commit-drafter/audits/9"
identifiers:
- type: other
value: "skillstore:abejitsu-commit-drafter:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a focused commit message
Generate a clear draft after staging one logical change set.
Standardize team commit summaries
Use staged diff context to draft messages with consistent structure.
Review contribution changes quickly
Create a readable draft before final review of staged open source changes.
Try These Prompts
Draft a commit message for my staged changes.
Draft a commit message for my staged changes with a concise summary line.
Create a commit message with What, Why, and How sections for the staged changes.
Review the staged diff context, draft a commit message, and note any issues I should check before committing.
Best Practices
- Stage only files that belong in one logical commit.
- Review the drafted message before committing.
- Remove secrets from staged changes before using AI review.
Avoid
- Do not use one draft for unrelated changes.
- Do not accept generated messages without checking accuracy.
- Do not stage secret files before drafting a message.