Skills commit-message
📦

commit-message

Content revision r1 Safe ⚙️ External commands

Write Better Git Commit Messages

Inconsistent commit messages make reviews and release notes harder to scan. This skill formats concise Conventional Commit summaries with clear 72-column bodies.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "commit-message" from https://skillstore.io/skills/chemiseblanc-commit-message.md and its manifest at https://skillstore.io/api/skills/chemiseblanc-commit-message/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.

Markdown detail GET /skills/chemiseblanc-commit-message.md Signed manifest GET /api/skills/chemiseblanc-commit-message/manifest Signed lockfile GET /api/skills/chemiseblanc-commit-message/lockfile

Test it

Using "commit-message". The parser now returns an empty result for blank input instead of failing.

Expected outcome:

fix(parser): handle empty input without panic

Blank input can appear when users submit optional fields. Returning an empty result keeps validation predictable and prevents avoidable request failures.

Using "commit-message". OAuth2 PKCE support was added for mobile and browser clients.

Expected outcome:

feat(auth): add OAuth2 PKCE flow support

Mobile and browser clients cannot safely store client secrets. PKCE lets these clients authenticate without relying on the insecure implicit flow.

Security Audit

Safe
v8 • 7/6/2026 Open versioned report

All static findings are false positives caused by Markdown code fences and inline commit-message examples. I found no prompt injection, data exfiltration intent, network behavior, or executable script instructions in SKILL.md.

1
Files scanned
84
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (14)
SKILL.md:12-14 SKILL.md:14-16 SKILL.md:16 SKILL.md:19 SKILL.md:33-36 SKILL.md:36-40 SKILL.md:40 SKILL.md:46-48 SKILL.md:48-52 SKILL.md:52-61 SKILL.md:61-65 SKILL.md:65-73 SKILL.md:73-77 SKILL.md:77-83
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/chemiseblanc-commit-message/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/chemiseblanc-commit-message/security.svg)](https://skillstore.io/skills/chemiseblanc-commit-message?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/chemiseblanc-commit-message?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/chemiseblanc-commit-message/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/chemiseblanc-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>
Academic citations (APA · BibTeX · CFF)

APA citation

Chemiseblanc. (2026). commit-message security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/chemiseblanc-commit-message/audits/8

BibTeX citation

@techreport{chemiseblanc-chemiseblanc-commit-message-2026, author = {Chemiseblanc}, title = {commit-message security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/chemiseblanc-commit-message/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 security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "Chemiseblanc" date-released: "2026-07-06" url: "https://skillstore.io/skills/chemiseblanc-commit-message/audits/8" identifiers: - type: other value: "skillstore:chemiseblanc-commit-message:audit:8" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
85
Content
71
Community
91
Spec Compliance

What You Can Build

Draft a Commit Message

Turn a change summary into a concise Conventional Commit message with a useful body.

Normalize Patch Submissions

Rewrite long or inconsistent commit text before review while keeping the technical intent clear.

Prepare Release History

Create consistent commit text that is easier to read when building changelogs.

Try These Prompts

Basic Commit Message 
Write a commit message for these changes: [describe changes]. Use the commit-message skill.
Commit With Scope 
Format this as a Conventional Commit with scope [component]: [describe the change and motivation].
Commit Body From Diff Notes 
Create a commit message from these diff notes. Explain the reason, user impact, and any measurable improvement.
Review Existing Message 
Review this commit message against the skill rules, then rewrite it if needed: [paste message].

Best Practices

  • Provide the diff summary and motivation before asking for a message.
  • Name the affected component so the scope can be accurate.
  • Mention user impact and measurable results for the body.

Avoid

  • Do not ask for trailers if the project requires this skill's no-trailer style.
  • Do not provide only file names without explaining behavior changes.
  • Do not use vague summaries such as update code or fix issue.

Frequently Asked Questions

Does this skill run Git commands?
No. It only gives formatting guidance for commit messages.
Which commit style does it use?
It combines Conventional Commit summaries with clear, kernel-style body text.
Can it write breaking-change messages?
Yes. It uses the exclamation marker before the colon when a change is breaking.
Does it include Signed-off-by trailers?
No. The skill explicitly tells users to omit commit trailers.
What input works best?
A short change summary, affected component, reason for the change, and user impact work best.
Can it review an existing message?
Yes. Ask it to check the message against the rules and rewrite it if needed.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/Chemiseblanc/ai/tree/main/skill/commit-message

Ref

dd4a3ef9f20ddf38830950b4bb713df96b431fd6

Maintenance freshness

7/18/2026

Usage

7 downloads · 252 views

File structure

📄 SKILL.md

More from Chemiseblanc

View all

Related Skills

View all